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
It's already difficult to rewrite tsconfig.json (to keep the filesGlob in sync). People have complained about merge conflicts #266 and options like formatting : #678
I'm cool with it, but I can see it breaking a lot of peoples workflows after exploring some of the issues here around tsconfig. Maybe we need to pull it into tsconfig and/or provide a CLI for those users, but note a comment caveat. Or just leave it as an option and disable it going forward.
For tooling, anything using tsconfig will continue support filesGlob. I don't think there's much using it though, so everything else will not work. Not sure how many people are relying on the expansion, the hope is not many to none.
I like the current behavior, but I'm not going to fight for it if you're unwilling to support it anymore. I do think that it would be fine to have the default atom-typescript-created tsconfig.json exclude node_modules and to not use the files or filesGlob properties, for example.
Tsconfig now supports comments : https://github.com/Microsoft/TypeScript/pull/5450/files
It's already difficult to rewrite tsconfig.json (to keep the filesGlob in sync). People have complained about merge conflicts #266 and options like formatting : #678
I'm thinking of disabling
files
rewriting permanently thoughts? @blakeembrey @nycdotnetThe text was updated successfully, but these errors were encountered: