We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
For one project of mine, flow check outputs:
flow check
src/controllers/auth.js:49 49: server.route(route.createPostRoute('/login', 'auth', { ^ call of method `createPostRoute` 33: config: RouteConfiguration ^^^^^^^^^^^^^^^^^^ property `tags`. Property not found in. See: src/utils/route.js:33 49: server.route(route.createPostRoute('/login', 'auth', { ^ object literal
The issue is totally valid, but the problem is that when I look at my Errors listing, it mixes up the "see also" and the actual error sites:
Instead of leading to src/controllers/auth.js, clicking on that errors leads me to where createPostRoute is defined, which is not helpful.
src/controllers/auth.js
createPostRoute
The text was updated successfully, but these errors were encountered:
Would #47 fix this for you? It adds an error for each file mentioned in a Flow error.
Sorry, something went wrong.
Yeah, I reckon it would! And if the entries appear in order, it would ensure the actual error site comes first in the list which is nice.
#47 won't fix this I think, it would still show just one error.
in microsoft/vscode#1927 (comment) they show that you can have a multi-line description, but only with one line showing in the "problems" section.
So perhaps that is the key
No branches or pull requests
For one project of mine,
flow check
outputs:The issue is totally valid, but the problem is that when I look at my Errors listing, it mixes up the "see also" and the actual error sites:
Instead of leading to
src/controllers/auth.js
, clicking on that errors leads me to wherecreatePostRoute
is defined, which is not helpful.The text was updated successfully, but these errors were encountered: