-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Standardize tsconfig.json for all packages #5276
Comments
@xirzec & @ramya-rao-a I tried to do this for cosmosdb/cosmos but the number of errors and API changes is just too much for a quick pass. I will skip it for now. |
Marked sdk/core/logger as done since somebody already did it. |
Marked sdk/template/template since it seems to already be standardized. |
@deyaaeldeen, Please check what is pending here and lets get this done! |
@deyaaeldeen I don't think a file by file approach will work for Cosmos. We either need to do it all in a single PR or do something like VSCode did where they look at the dependency graph and start at the edges. |
Hi @xirzec, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support. |
Right now packages have different tsconfig.json settings, especially around strictness flags.
We should have all configs inherit from a common config that enforces the right level of strictness checks.
Packages to tackle:
The text was updated successfully, but these errors were encountered: