-
Notifications
You must be signed in to change notification settings - Fork 76
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
Stricter typescript rules #161
Comments
Hey, thanks for the interest! I haven't digged too much into it but my idea was to try to remove as much rules as I can from the tsconfig file. Ideally be able to run fireorm with strict: true but it wouldn't be entirely possible |
Ok. I will play around with the |
Working on the strict migration I realized how much of a daunting task that is 😅. Do you guys think it would be possible to take an incremental approach to this migration, something similar to this comment? |
That sounds good! I'm working in a PR that will get rid a lot of errors, might be a good idea working after I'm done with it 😅 |
Update: merged #165 |
Addressing this comment. I'm thinking of doing on a folder-by-folder manner. With that in mind, here is the work pending:
To make a folder or file strict we just need to add it to the include cause in the inner tsconfing.json and fix the errors. After all the files are migrated we can remove the inner tsconfig and add the |
Will work on the |
I saw in #1
v1 Roadmap
section that theStricter typescript rules
is available. If no one is working on it I'm interested in tackling this 😃. @wovalle can you elaborate about this issue?The text was updated successfully, but these errors were encountered: