We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We need to send a subset of Cypress config data to the protocol so that the protocol can flex its behavior based on config values.
This will help support things like knowing the dev server route to be aware of what traffic is involved in loading component testing specs.
Part of this issue's work will be to figure out the exact set of data that we want to send.
The text was updated successfully, but these errors were encountered:
Released in 13.16.0.
13.16.0
This comment thread has been locked. If you are still experiencing this issue after upgrading to Cypress v13.16.0, please open a new issue.
Sorry, something went wrong.
ryanthemanuel
Successfully merging a pull request may close this issue.
What would you like?
We need to send a subset of Cypress config data to the protocol so that the protocol can flex its behavior based on config values.
Why is this needed?
This will help support things like knowing the dev server route to be aware of what traffic is involved in loading component testing specs.
Other
Part of this issue's work will be to figure out the exact set of data that we want to send.
The text was updated successfully, but these errors were encountered: