-
Notifications
You must be signed in to change notification settings - Fork 8
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
Simplify Zombienet SDK DX #251
Comments
Feel free to assign this issue to me. I'll submit a draft PR to have the discussion there and keep this issue compact for newcomers. |
On this, I'd re-export all I keep needing to add more stuff to the |
I think we coukd re-export the crates or in this case just create the wrappers as part of the sdk crate itself. Thoughts @ozgunozerk ? |
I don't have any strong preferences, as you guys see fit! @pepoviola I want to start on the implementation, did you have a chance to check out the draft PR for the more elaborate and concrete API design? |
Update: I have something ready, will polish it and submit it soon! |
Is your feature request related to a problem? Please describe.
Current state of
zombienet-sdk
is feature-rich, but lacks ease of use for many setting that can be hidden for most of the users by utilizing defaults.Simplifying the devx may increase and improve adoption, popularity, and open-source contribution.
Describe the solution you'd like
What I have in mind is roughly:
Describe alternatives you've considered
No response
Additional context
We met with @pepoviola and we are on the same page.
We want to preserve the
builder
andtype-state-pattern
, to enforce compile time checks and errors for the users.This feature will not rewrite everything from scratch, but will act as a wrapper on top of the current code. Thus, preserve the safety measures that are already there
The text was updated successfully, but these errors were encountered: