-
Notifications
You must be signed in to change notification settings - Fork 3.3k
fix: remove baseUrl from root-level types for supported fields #20589
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
Conversation
Thanks for taking the time to open a PR!
|
Test summaryRun details
View run in Cypress Dashboard ➡️ FlakinessThis 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.
One minor comment/question. Thanks!
Cypress.config({ baseUrl: '.', }) // $ExpectType void | ||
Cypress.config({ e2e: { baseUrl: '.' }}) // $ExpectType void | ||
Cypress.config({ e2e: { baseUrl: null }}) // $ExpectType void | ||
Cypress.config({ e2e: { baseUrl: '.', }}) // $ExpectType void |
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.
do we need one of these tests asserting component.baseUrl
is not allowed? (I am not sure if these inline, string-based assertions support that)
User facing changelog
Update types with supported fields on the root level and with each testing type
Additional details
How has the user experience changed?
PR Tasks
cypress-documentation
?type definitions
?cypress.schema.json
?