-
Notifications
You must be signed in to change notification settings - Fork 9
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
Implement 'publishVersionIntent' #35
Conversation
Co-Authored-By: sohkai <qisheng.brett.sun@gmail.com>
* Publishes a new version (`version`) of `appId` using storage provider `provider`. | ||
* | ||
* If the destination repository does not exist, the intent will be for creating a new | ||
* repository with an initial version. |
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.
Is it a lot easier for the CLI to use a single function to do both version publishes as well as repo creations?
Really seems like there's two concerns mixed here (you can immedately tell by the manager
being the first argument, but it not being used at all on the "normal" path).
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.
Not necessarily, I think having something like:
if ( apm.getRepo() ) {
apm.publishVersion()
} else {
apm.publishInitialVersion()
}
is not more difficult, but actually more expressive 👍 (you don't have to guess the magic publishVersion
does).
That being said, refactoring this might take some time without adding a lot of value (especially if we want to keep backwards compatibility), so I will open an issue for it.
Co-Authored-By: 0x6431346e <hello@danielconstantin.net>
Implements a new
publishVersionIntent
function that returns an aragon.js intent object that can be used to publish a new version using transaction pathing.publishIntent
now usespublishVersionIntent
and still generates the direct transaction to publish a version, making the change fully backwards compatible.Closes #13