-
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
CT: cypress doesn't recognize "+" symbol in the path to the Angular component #29493
Comments
@jennifer-shehane Hello ! Can I solve this problem ? |
@H0onnn Yes, please follow our contributing guidelines and write a test for the behavior and we could review. |
@jennifer-shehane Hello, is there a way to check if the test works properly with the modified code in my local environment? |
@H0onnn @jennifer-shehane Hello, is there any progress on this issue? |
@bobige No, this is open to contributors if someone wants to make a PR though |
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. |
Current behavior
Importing an angular component into a test file, when the component folder name starts with a "+" symbol, is not possible.
Desired behavior
Cypress imports components that have the "+" symbol at the start of the containing folder name.
Test code to reproduce
Cypress Version
13.9.0
Node version
v16.18.1
Operating System
Windows 10.0.19045 Build 19045
Debug Logs
No response
Other
I am configuring Cypress to test Angular 15 components. We have a naming convention to put the "+" sign in front of the folder name, containing the component files. When I mount the component, cypress gives a "No tests found" error, which according to the documentation could be caused by a syntax error.
It is easily reproduceable. Create a new Angular 15 project and create a component in a folder that has the "+" sign in front of it. I also use Chrome 124:
If I remove the "+" sign or even change the naming to have a different special character, such as "_", it works:
The text was updated successfully, but these errors were encountered: