-
Notifications
You must be signed in to change notification settings - Fork 17
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
Make node publication API slicker #489
Milestone
Comments
#433 this already cleans up the addVolume methods. Maybe this issue could also be resolved there. |
#497 related |
I think it might be possible to close this since #497 |
@ctrueden is this closable? |
I haven't had time to play with the revised API yet, but would defer to others on whether they think it's friendly enough now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now the pattern is:
Would be nice if there were an API to make this pattern emerge automatically, by rolling the publication into one of the other API calls or some such.
If the idea is to "build up" the volume's structure before publishing the finished product, maybe we could use a builder pattern, or some kotlinesque/functional thing?
Such that publication happens when the
withConfig
finishes? There are surely a few different ways to pet this particular cat, just wondering if we can reduce the chance of forgetting to publish after setting things up.The text was updated successfully, but these errors were encountered: