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
When the user is creating a query, and the mode is set to "Fetch at any time". In the following cases:
Fetch: user sets method to something other than GET or HEAD
SQL: user writes a query other than SELECT
...?
This could potentially be valid (e.g. a server may accept a POST request for data fetching) so we shouldn't downright disallow it, but we may want to warn the user that it looks like they're defining a destructive query and that they probably want to set the mode to "Only fetch on manual action"
Additionally we may do some of the following to enlarge the pit of success
In the message, add a button that switches the mode
Pull attention to the mode selector in some way
Add a confirmation dialog when the user saves the query that explains the query will run automatically and confirms whether it's their intention
...?
Examples 🌈
No response
Motivation 🔦
No response
The text was updated successfully, but these errors were encountered:
Duplicates
Latest version
Summary 💡
When the user is creating a query, and the mode is set to "Fetch at any time". In the following cases:
GET
orHEAD
SELECT
This could potentially be valid (e.g. a server may accept a POST request for data fetching) so we shouldn't downright disallow it, but we may want to warn the user that it looks like they're defining a destructive query and that they probably want to set the mode to "Only fetch on manual action"
Additionally we may do some of the following to enlarge the pit of success
Examples 🌈
No response
Motivation 🔦
No response
The text was updated successfully, but these errors were encountered: