You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should prevent persisted queries from being saved if the query uses arguments but does not define variables for the arguments.
This will prevent situations where string concatenation is used instead of variables and a plethora of queries are stored instead of a singular query with variables.
We had 1 user use string concatenation that lead to 72,000 queries being stored.
i.e.
constPOST_ID=$something_dynamic_from_url_or_something;constquery=`query { post( id: ${POST_ID} idType: DATABASE_ID) { id title date }}`
This would create a different persisted query for every ID used because of the string interpolation.
We should prevent this query from being saved as a persisted query and a clear error message should be returned explaining why the persisted query cannot be saved.
The text was updated successfully, but these errors were encountered:
We should prevent persisted queries from being saved if the query uses arguments but does not define variables for the arguments.
This will prevent situations where string concatenation is used instead of variables and a plethora of queries are stored instead of a singular query with variables.
We had 1 user use string concatenation that lead to 72,000 queries being stored.
i.e.
This would create a different persisted query for every ID used because of the string interpolation.
We should prevent this query from being saved as a persisted query and a clear error message should be returned explaining why the persisted query cannot be saved.
The text was updated successfully, but these errors were encountered: