-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
IDE Persistent Parse does not handle tsconfigs with no "include" and no "files" with deeply nested folder structures #1110
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
Should be noted that the default I find myself having to change |
There is another workaround which would be a little less cumbersome - do something similar to what we do in this repo: you can declare your tsconfigs directly via a typescript-eslint/.eslintrc.js Line 117 in 7a8cce6
( That way you wouldn't have to modify the tsconfig, potentially breaking a build. |
I really appreciate your suggestions, workarounds, and time. Seriously, thank you. It's an annoying situation, where I either change all tsconfigs (and risk further breakage) or add new ones with maintainability burden. I'm not sure which is better. Some repos already have a separate tsconfig for the build (in each package!), and adding further ones feels wrong. I'll try to assist and dive into the code a bit, hoping I won't drown... :) |
Spinning off of #1080 (comment)
if you provide a tsconfig without "includes" (or "files"), I.e. an empty tsconfig:
{}
, then typescript uses a different codepath to setup the folder watchers.Triggering a directory change does not work the same was as when the tsconfig has "includes".
It won't block the release on Monday, as it's an edge case of sorts, but I'll need to look deeper into it to figure out how it all works!
The text was updated successfully, but these errors were encountered: