-
Notifications
You must be signed in to change notification settings - Fork 28
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
Add a guide for TypeScript #599
Conversation
There are some pitfalls with using Effection and TypeScript together. While we can't fix them, we can at least explain what they are and ways that you can mitigate them.
@cowboyd what do you think about this instead
|
@taras Feels great! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I definitely like the unwrap
helper 👍
I don't think it would do any harm. If generators were more mainstream then they would do something. |
I'm going to go ahead and merge. @taras LMK if you have any feedback on the CTA at the end and I'll submit another PR. |
Motivation
There are some pitfalls with using Effection and TypeScript together, and with the expectations of type-safety that come with TypeScript, it can be one of the biggest stumbling blocks to adoption. While we can't fix them directly (only the TypeScript team can do that), we can at least explain what they are, why they can't be fixed by anybody but the TypeScript team, and ways that you can mitigate them.
Approach
I tried to just enumerate the challenges that we've encountered, and propose some of the solutions.
Things I'm not entirely sure of: