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
Per today, source maps aren't / can't be utilized. EG. when multiple step definitions match, we throw an error
Error: Multiple matching step definitions for: a step a step /a step/
.. while cucumber-js on the other hand, would throw something like
Multiple step definitions match: a step - features/step_definitions/cli_steps.ts:44 /a step/ - features/step_definitions/cli_steps.ts:49
Furthermore, we just output dummy object in the JSON reports.
{ "match": { "location": "not available:0" } }
The text was updated successfully, but these errors were encountered:
For reference, a PoC is avaliable in the branch source-map, but I'm waiting on evanw/esbuild#2218 to see if there's a smoother way of handling paths.
source-map
Sorry, something went wrong.
I'm guessing this is the same issue preventing this user from seeing the stack trace? cypress-io/cypress#23563
No, this is an entirely separate issue.
No branches or pull requests
Per today, source maps aren't / can't be utilized. EG. when multiple step definitions match, we throw an error
.. while cucumber-js on the other hand, would throw something like
Furthermore, we just output dummy object in the JSON reports.
The text was updated successfully, but these errors were encountered: