-
Notifications
You must be signed in to change notification settings - Fork 443
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
Replace drink sandbox by internal ink_sandbox #2158
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2158 +/- ##
==========================================
+ Coverage 53.64% 54.20% +0.56%
==========================================
Files 225 231 +6
Lines 7095 7204 +109
Branches 3129 3153 +24
==========================================
+ Hits 3806 3905 +99
- Misses 3289 3299 +10 ☔ View full report in Codecov by Sentry. |
🦑 📈 ink! Example Contracts ‒ Changes Report 📉 🦑These are the results when building the
Link to the run | Last update: Tue Mar 19 16:52:03 CET 2024 |
Won't this become a maintenance problem? Previously, when we wanted to extend capabilities of drink! we had to do it only for that one crate - drink! itself - now, there are two sandboxes - drink's and ink's. How do you envision the future of the tool if one of its biggest users is now ink! itself? |
@deuszx to be clear, the goal is to move the shared part to ink!, not to duplicate the trait. The follow up will be to remove the code in drink! repo and use ink_sandbox as a dependency instead. I agree that this is moving the maintenance burden, from one repo to the other, but because drink! already has (indirect) dependency on the ink! repo, it would make the overall maintenance much easier if we re-organize the dependency as suggested here. What do you think? |
e3ca10f
to
6d31e86
Compare
6d31e86
to
da422c6
Compare
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.
Making the comment style consistent with the codebase.
Co-authored-by: Michael Müller <[email protected]>
Co-authored-by: Michael Müller <[email protected]>
Co-authored-by: Michael Müller <[email protected]>
Co-authored-by: Michael Müller <[email protected]>
Co-authored-by: Michael Müller <[email protected]>
Co-authored-by: Michael Müller <[email protected]>
Co-authored-by: Michael Müller <[email protected]>
Co-authored-by: Michael Müller <[email protected]>
drink! side of the migration inkdevhub/drink#119 |
From my perspective looks good but let's consider separating release cycles of Sandbox and ink! as you mentioned in the comment. |
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.
LGTM
Thank you @pmikolajczyk41 @deuszx ❤️
fe7bc27
to
1175740
Compare
I have excluded ink_sandbox from the release and added a note to the release, not sure if there is a better way to do it See relevant commit here |
Remove the drink dependency, and move the drink::Sandbox to it's own package.