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
Override API Response is a very handy feature for frontend developers to unblock themselves from backend developers, simulate API errors, override configs, test negative cases, etc. but the responses overridden by Requestly aren't captured in Chrome Devtools so it always creates confusion for the end users whether the rule has applied or not.
Here are a few changes we are doing to improve the overall experience of testing a rule.
When the user saves the rule for the first time, give the visibility to testing feature
Auto-Save sessions when a user comes back to the rule editor, the user can view and delete the session.
Remove Execution Logs
Show a widget on the page whenever a rule is applied and by default keep it on for Script Rule, Response Rule and let user configure for other rule types.
The text was updated successfully, but these errors were encountered:
Override API Response is a very handy feature for frontend developers to unblock themselves from backend developers, simulate API errors, override configs, test negative cases, etc. but the responses overridden by Requestly aren't captured in Chrome Devtools so it always creates confusion for the end users whether the rule has applied or not.
Here are a few changes we are doing to improve the overall experience of testing a rule.
The text was updated successfully, but these errors were encountered: