-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support dynamically disabling request logs via cy.intercept()
#26069
Labels
Comments
flotwig
added
type: enhancement
Requested enhancement of existing feature
topic: cy.intercept()
labels
Mar 9, 2023
3 tasks
Make sure to update the docs when this issue is closed in the future. cypress-io/cypress-documentation#5106 |
Any updates on this? |
It would be nice to have an option to log only when there is an error. |
Other options are:
Obviously thorough analysis is necessary to check if these signatures are not dubiously conflicting with the existing signature. |
Argh, also needed this to make my logs look a bit prettier. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
What would you like?
Add the ability to dynamically disable request logs in cy.intercept(), like so:
Why is this needed?
#25547 adds the ability to control
log
viaStaticResponseWithOptions
. However, this can only be done statically, not dynamically via an interceptor function.The reasons why it was done this way are detailed in the original ClickUp initiative. TL;DR: dynamically setting
log
can cause a log to be hidden/shown asynchronously, which requires making some hard UI decisions about how to indicate this at each step.Other
No response
The text was updated successfully, but these errors were encountered: