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

Typescript example recipe workflow #1356

Closed
matt-psaltis opened this issue Feb 21, 2018 · 4 comments
Closed

Typescript example recipe workflow #1356

matt-psaltis opened this issue Feb 21, 2018 · 4 comments
Labels

Comments

@matt-psaltis
Copy link

matt-psaltis commented Feb 21, 2018

Current behavior:

Using the Webpack with Typescript example recipe, Typescript compilation issues cause the plugin to crash. This brings you to the following screenshot.

image
(Image edited to remove sensitive information)

Additionally, the Try Again button on the Cypress app is at the bottom of the error message. When the error is quite lengthy, I spend a decent amount of time scrolling or using keyboard shortcuts to get to the bottom of the window so that I can click the Try Again button.

Desired behavior:

The plugin doesn't crash due to compilation issues. It keeps monitoring for changes and the Typescript compilation issues are displayed in the running browser session.

The Try Again button remains above the error message to reduce the time needed to restart the plugin.

How to reproduce:

Using the Webpack with Typescript recipe, add random text to the spec file such that the text cannot be resolved as a valid command or statement.

  • Operating System: Windows 10
  • Cypress Version: 2.0.2
  • Browser Version: Chrome 64
@brian-mann
Copy link
Member

I know we currently watch the file for changes - after you introduce an error and then revert the problem (and get back to working code) does it automatically update or do you have to click "Try Again" ?

@matt-psaltis
Copy link
Author

Yeah, had the same thought. For me, it's stopped watching. I always have to click try again even when the compilation error has been resolved.

@brian-mann
Copy link
Member

@chrisbreiding ^^

@chrisbreiding chrisbreiding self-assigned this Feb 22, 2018
@jennifer-shehane jennifer-shehane added the stage: proposal 💡 No work has been done of this issue label Mar 8, 2019
@jennifer-shehane
Copy link
Member

Closing as resolved.

If you're experiencing a bug similar to this in Cypress, please open a new issue with a fully reproducible example that we can run. There may be a specific edge case with the issue that we need more detail to fix.

@cypress-io cypress-io locked as resolved and limited conversation to collaborators Mar 3, 2020
@jennifer-shehane jennifer-shehane removed the stage: proposal 💡 No work has been done of this issue label Mar 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants