-
-
Notifications
You must be signed in to change notification settings - Fork 681
return-in-computed-property error not triggered #173
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
Comments
armano2
added a commit
to armano2/eslint-plugin-vue
that referenced
this issue
Sep 4, 2017
@lgodard Nice catch, issue is with order how queries are executed -> |
verified, it works like a charm |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi all,
I try the eslint plugin and the
return-in-computed-property
is not triggered on a test fileESLint config
What did you do? Please include the actual source code causing the issue.
$ eslint . --ext .js,.vue
targetting this source file triggering an error
What did you expect to happen?
the computed property
my_FALSE_test
should be reported as faultyWhat actually happened? Please include the actual, raw output from ESLint.
the file is analyzed, but no error reported. nothing returned
digging further, in plugin source code
at this line
eslint-plugin-vue/lib/rules/return-in-computed-property.js
Line 26 in 3ed8c5c
here is the state of the variables (console.log output)
my understanding (though i may be wrong) is that
utils.executeOnFunctionsWithoutReturn
does not parse the file correctly and does not detect the computed propertyIs it something I do wrong ?
Feel free to ask if more info needed
Thanks !
Laurent
The text was updated successfully, but these errors were encountered: