-
Notifications
You must be signed in to change notification settings - Fork 43
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
Move to Typescript #89
Comments
yes, I have some regret not starting off with typescript and have been postponing the refactor effort. I've added it to my backlog list for tracking, but I have a few features I've committed to first. |
If it's alright with you I'd like to move to strict = false first, this makes most JavaScript okay for TypeScript. That way the types can follow organically. I'd like to help out with this change. Are your unmerged branches very different from main? |
I currently only have two relevant branches: I appreciate any help with the migration towards typescript. thank you. |
rnr has been a huge help |
Thus I'm unable to debug what is going wrong, currently running the frontend requires debugging minimized code.
This where my participation ends, I hope I've given you some helpful advice |
Yes, I understand. For my reference can you point me to an example of your point 2 and what you would have expected to see instead. Thanks for your advice. |
Instead of using absolute imports like "components/card.tsx" use "src/components/card.tsx" or "~/src/components/card.tsx" I attempted to add each dir in src as a base in my configs but it just becomes a buggy mess. |
Okay I see what you mean. I appreciate all of your advice and will incorporate it as I go forward. |
I'd like to use this project in a different project, I'd need to build an sdk based off the app/mobile/src/api files. Even then I'd be coding in the dark without types. A good first step would be to move to Typescript.
The text was updated successfully, but these errors were encountered: