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.

Sign up for GitHub

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

Jump to bottom

Eclipse Che JS Linter doesn't analyze the JS code on the fly. #4886

Closed
sr229 opened this issue Apr 23, 2017 · 9 comments
Closed

Eclipse Che JS Linter doesn't analyze the JS code on the fly. #4886

sr229 opened this issue Apr 23, 2017 · 9 comments
Assignees
@AndrienkoAleksandr
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.

Comments

@sr229
Copy link
Contributor

sr229 commented Apr 23, 2017

Whenever I edit a JS File, the linter has to always wait for the save event to update it's analysis. It wuld be nice if the JS Linter lints on the fly without waiting for the file to be saved.
@ghost
Copy link

ghost commented Apr 23, 2017

@sr229 doesn't auto save help the situation? As soon as you stop typing, the linter shows you errors.

@ghost ghost added the kind/question Questions that haven't been identified as being feature requests or bugs. label Apr 23, 2017
@sr229
Copy link
Contributor Author

sr229 commented Apr 25, 2017

@eivantsov it does a bit but the linter should always lint IMHO regardless if the file changed is saved or not. Take for example, Cloud9's JS Linter which observes unsaved file changes and lints it without waiting for the file to be saved.

@ghost ghost added kind/enhancement A feature request - must adhere to the feature request template. kind/bug Outline of a bug - must adhere to the bug report template. severity/P2 Has a minor but important impact to the usage or development of the system. and removed kind/question Questions that haven't been identified as being feature requests or bugs. kind/enhancement A feature request - must adhere to the feature request template. labels Apr 25, 2017
@ghost
Copy link

ghost commented Apr 25, 2017

Marking it as a bug since for me, linting does not show errors on the go and the file needs to be closed and opened to see errors. This makes all Orion js support pretty much useless.

@ghost ghost mentioned this issue Apr 28, 2017
Closed
@sr229
Copy link
Contributor Author

sr229 commented Jul 11, 2017

Can verify the said issue at my end. Orion's JS support does not work in Codenvy 5.14.0

@ghost
Copy link

ghost commented Jul 11, 2017

Even though I wouldn't say that

Orion's JS support does not work in Codenvy 5.14.0

this is a nasty bug indeed.

@ghost ghost added severity/P1 Has a major impact to usage or development of the system. and removed severity/P2 Has a minor but important impact to the usage or development of the system. labels Jul 12, 2017
@ghost ghost mentioned this issue Jul 12, 2017
Closed
@ghost ghost added the team/ide label Jul 12, 2017
@sr229
Copy link
Contributor Author

sr229 commented Nov 8, 2017

Might be able to be fixed by #5330 as Monaco has native JS support.

@SkorikSergey
Copy link
Contributor

Is this still an issue?

@sr229
Copy link
Contributor Author

sr229 commented Jan 27, 2018

@SkorikSergey it's persistent on my end, probably a Orion-related bug

@vparfonov vparfonov mentioned this issue Feb 12, 2018
Closed
27 tasks
@ghost
Copy link

ghost commented May 10, 2018

Closing as it cannot be solved on Che side.

@ghost ghost closed this as completed May 10, 2018
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AndrienkoAleksandr AndrienkoAleksandr

Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@AndrienkoAleksandr @SkorikSergey @sr229