Skip to content
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

Marketplace move hashVersion #894

Closed
wants to merge 6 commits into from
Closed

Conversation

NicolasMahe
Copy link
Member

Dependant on #864.
Closes #861.

This PR move the hashVersion from the manifest data to the service definition. Like this, the core itself can manage the version used to calculate the service's hash.

…tplace-move-hashVersion

# Conflicts:
#	systemservices/marketplace/mesg.yml
@NicolasMahe
Copy link
Member Author

@mesg-foundation/core ready to review

@NicolasMahe
Copy link
Member Author

@antho1404 do you agree with this modification?

@antho1404
Copy link
Member

let's rename hashVersion into version this is a version of a service not only the hash

@@ -27,6 +27,9 @@ type Service struct {
// It represents the service uniquely.
Hash string `hash:"-"`

// HashVersion is the version of the algorithm used to calculate the of the hash
HashVersion string `hash:"-"`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think hash:"-" is used anymore but just to keep in consistent, let's pretend it is and in that case the version is required in the hashing

@NicolasMahe
Copy link
Member Author

Closing in favor of #906

@NicolasMahe NicolasMahe deleted the ss/marketplace-move-hashVersion branch April 22, 2019 09:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Move marketplace's hashVersion in the core
4 participants