-
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
Allow passing qs parameter to cy.visit to set querystring #5040
Conversation
Test summaryRun details
View run in Cypress Dashboard ➡️ This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't personally like the name of this argument being qs
. It doesn't seem immediately obvious what qs stands for.
I liked the original issues suggestion of passing in the arg as params
.
BUT, I'm also perhaps not as familiar with other existing APIs in this space - so if this is a really common convention then 🤷♀
packages/driver/test/cypress/integration/commands/navigation_spec.coffee
Show resolved
Hide resolved
I'm fine with |
Actually, cy.request() uses |
@flotwig Oh 😞 I didn't realize this was supported in cy.request, |
…#5040) * allow passing qs param to cy.visit * add types * qs -> params, merge with url, throw errors on invalid type, add tests * params -> qs * cleanup * fix test
Pre-merge Tasks
cypress-documentation
been submitted to document any user-facing changes? Add cy.visit() qs option cypress-documentation#2042