-
Notifications
You must be signed in to change notification settings - Fork 376
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
dappkit deprecation #10207
Comments
Tagging @celo-org/default-owners |
Reflecting discussion from weekly sync:
Note:
|
WIP findings https://www.notion.so/clabsco/WIP-celo-contractkit-830cce5acffe4d65bbe9a61724364f63, I will keep updating that doc as I gather more info |
Scheduled a call with Valora which seems to be the only users of dappkit to talk about sunsetting |
Dappkit sunsetting post https://forum.celo.org/t/sunsetting-dappkit/5336 |
Contractkit public sunsetting post https://forum.celo.org/t/sunsetting-contractkit/5337 |
Todo following the two blog posts:
Context:
|
|
Migration guide Removal of dappkit |
Closing this and following issue specific to contractkit can be found here: #10289 |
Following this convo:
Hello there, the topic of "moving the core-contract types so they can more easily be imported in typescript" has come up again during the apptooling meeting and we're gonna try to separate into their own package. The only question is whether to move them to a different package or even outside of the monorepo.
The current trend seems to be to cleanup the monorepo a bit, but having the types stay here actually makes tons of sense (no tooling to reinvent, no submodules to handle)
Any thoughts?
The text was updated successfully, but these errors were encountered: