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

fix(template): mark the entire expression as invalid when the linter finds an error #88

Closed
mgechev opened this issue Sep 18, 2016 · 0 comments
Assignees
Labels

Comments

@mgechev
Copy link
Owner

mgechev commented Sep 18, 2016

Currently the sourceSpan produced by the template parser doesn't show a detailed enough information of where exactly a propertyRead, propertyWrite or a methodCall is. Another bonus of marking the entire expression as invalid is to have a more visible (as being also longer in terms of characters) notification produced by the text editor.

@mgechev mgechev added the bug label Sep 18, 2016
@mgechev mgechev self-assigned this Sep 18, 2016
@mgechev mgechev added this to the Beta 1 milestone Sep 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant