-
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 users to change spec path before it is created from component #25005
Comments
Hey team! Please add your planning poker estimate with Zenhub @amehta265 @lmiller1990 @marktnoonan @mike-plummer @rockindahizzy @warrensplayer @ZachJW34 |
Can't you already do this? What are the edge cases? I just tried it out - you choose your component, then you can change the spec path to whatever you like. I don't understand the change - are we just swapping the order of the two steps? |
Do we always show the user-editable path after clicking on a component or only when an error occurs when generating a name? |
@ZachJW34 i think the idea was to always show it |
This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided. |
This issue has been closed due to inactivity. |
What would you like?
Currently when users create a spec from a component, we auto-generate a file name and path for them. There are some edge cases where this can lead to confusing experiences with specs being placed in an unexpected location or with a confusing spec name.
Before the spec file is created, we should show the "blank spec" modal with the path where we would put the generated spec file and give the user the opportunity to change the path (as long as it conforms to the spec pattern) before proceeding with generating the spec file.
This screen already exists for generating blank specs, so we should be able to re-use the UI for this purpose.
The text was updated successfully, but these errors were encountered: