-
Notifications
You must be signed in to change notification settings - Fork 5
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
Adding Typescript Support #2
Comments
Hey @RageBill, sorry for the delay in getting back to you. Hope this didn't cause you too much frustration. I'd be more than happy to incorporate TypeScript support, unfortunately I'm just not right person to do it. I haven't gotten around to learning TypeScript just yet, so I'm missing the groundwork in understanding what performing a migration like this might look like. In addition, I think if we were to add TypeScript support we'd probably need to lock down the arguments that the Rough.js Would it be possible for you to make a new branch and add the foundation TypeScript? Like, if you port over a single component and add the compiler stage, I'll be happy to learn from that and migrate the rest over? |
Hi @cawfree , thanks for the reply! It is completely understandable during such busy times. I will make a pull-request for a typescript branch and see what we can do about it! I am new to this awesome library (when I saw your post on Reddit), so I might not be able to type everything. I will leave a few TODOs here and there for fixing in the future - I'll kick start it first :) |
@RageBill That's wicked man, thank you for understanding! Sounds like a plan. 👍 Please don't feel obligated to do too much, I'm more than happy to build on your foundations and then just run past you for a quick sanity check. Thanks again! |
Would you consider using Typescript or add typing to support Typescript usage?
There are existing typing available in the react-rough library, plus the project uses prop-types already, so it doesn't seem too much work to add support here.
Thank you!
The text was updated successfully, but these errors were encountered: