Skip to content
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

"Open in IDE" in custom commands should show from where custom command was called #26520

Open
marc-guenther opened this issue Apr 17, 2023 · 0 comments
Labels
type: feature New feature that does not currently exist type: user experience Improvements needed for UX

Comments

@marc-guenther
Copy link

Current behavior

When a test fails inside a custom command, there appears a link with the "Open in IDE" tooltip, which when clicked, opens the source file where my custom command is defined.

Desired behavior

What is usually more important is where this custom command was called from. I would think it would appear in the "View stack trace" as the second line, but there only the first line is clickable, which also opens the custom command.

It would be nice to have some way to open the source file which called the custom command instead of opening the custom command itself. We have some commands which are called very frequently from all over the place, which means the "Open in IDE" is quite useless for us.

Which is a pity as it is such a cool idea and such a time saver outside of custom commands.

Test code to reproduce

Only the first entry in the stack trace is clickable (the one starting with webpack). The rest I would expect to somewhere show the place from where the custom command was called, but there is nothing to be found there.
image

Cypress Version

v12.9.0

Node version

v19.1.0

Operating System

10.15.7

Debug Logs

No response

Other

No response

@nagash77 nagash77 added type: feature New feature that does not currently exist DX labels Apr 17, 2023
@jennifer-shehane jennifer-shehane added type: user experience Improvements needed for UX and removed DX labels Oct 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature New feature that does not currently exist type: user experience Improvements needed for UX
Projects
None yet
Development

No branches or pull requests

3 participants