Skip to content

How to make parser work on plain js files. #109

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

Closed
armano2 opened this issue Jul 26, 2017 · 1 comment · Fixed by #123
Closed

How to make parser work on plain js files. #109

armano2 opened this issue Jul 26, 2017 · 1 comment · Fixed by #123

Comments

@armano2
Copy link
Contributor

armano2 commented Jul 26, 2017

I looked into my projects and i found out one missing functionality here, sometimes we can create abstract components in js files with no template, with or without render function and in that case eslint is not going to work with this file because he don't know that this is a component.

Solution:
I propose to add a way to instruct parser to treat files with comment /* @vue/component */ as vue components.

@michalsnik
Copy link
Member

I like this idea 👍 We're not able to catch all scenarios and this would definitely help.

armano2 added a commit to armano2/eslint-plugin-vue that referenced this issue Aug 2, 2017
@michalsnik michalsnik added this to the Official release milestone Aug 3, 2017
armano2 added a commit to armano2/eslint-plugin-vue that referenced this issue Aug 4, 2017
armano2 added a commit to armano2/eslint-plugin-vue that referenced this issue Aug 4, 2017
armano2 added a commit to armano2/eslint-plugin-vue that referenced this issue Aug 6, 2017
michalsnik pushed a commit that referenced this issue Aug 8, 2017
* Allow to use @vue/component to set enable parsing vue objects
fixes #109

* Add support for eslint 4.x
LineComment and BlockComment was removed in 4.0.0

* Remove unessesery function
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment