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
This is probably something that could be done through core. Effectively per route and then method on that route.
In Restsplain terms we could do background requests to each route, probably just with GET methods (with the exception of generating proper required params, no url type for example). Then we could check the responses for error codes and if it's a 401 add some data about that route and show a padlock icon.
It's a lot of requests but ok in the background perhaps.
The text was updated successfully, but these errors were encountered:
This is probably something that could be done through core. Effectively per route and then method on that route.
In Restsplain terms we could do background requests to each route, probably just with
GET
methods (with the exception of generating proper required params, nourl
type for example). Then we could check the responses for error codes and if it's a 401 add some data about that route and show a padlock icon.It's a lot of requests but ok in the background perhaps.
The text was updated successfully, but these errors were encountered: