-
Notifications
You must be signed in to change notification settings - Fork 13
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
Conversation
…tplace-move-hashVersion # Conflicts: # systemservices/marketplace/mesg.yml
@mesg-foundation/core ready to review |
@antho1404 do you agree with this modification? |
let's rename |
@@ -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:"-"` |
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.
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
Closing in favor of #906 |
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.