You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that with xojs/xo#348xo did indeed have problems with typescript files.
So from what I gathered in that issue the linting for ts files has been disabled.
And indeed running $ npx xo on the project yields no errors (the *.d.ts file seems (to me) ignored from linting).
But this extension really likes typescript files, so it tries to lint it regardless 😆.
Searching for issues of a similar kind, I found that the solution provided in #53 works for me too.
For reference, in the package.json file I added the following snippet (I have a single typescript definition file):
"xo": {
"ignores": [
"*.d.ts"
]
}
Finally, the question: could the extension ignore typescript files just as the xo CLI seems to do?
FWIW I may be thinking the wrong thing on the xo CLI of course.
If you need a repository for reproducing the "error", feel free to ask me and I'll gladly provide you the one I am using.
The text was updated successfully, but these errors were encountered:
First, some env info (taken from VS Code):
XO-specific info:
Now to the problem.
I noticed that with xojs/xo#348
xo
did indeed have problems with typescript files.So from what I gathered in that issue the linting for ts files has been disabled.
And indeed running
$ npx xo
on the project yields no errors (the*.d.ts
file seems (to me) ignored from linting).But this extension really likes typescript files, so it tries to lint it regardless 😆.
Searching for issues of a similar kind, I found that the solution provided in #53 works for me too.
For reference, in the
package.json
file I added the following snippet (I have a single typescript definition file):Finally, the question: could the extension ignore typescript files just as the xo CLI seems to do?
FWIW I may be thinking the wrong thing on the xo CLI of course.
If you need a repository for reproducing the "error", feel free to ask me and I'll gladly provide you the one I am using.
The text was updated successfully, but these errors were encountered: