-
Notifications
You must be signed in to change notification settings - Fork 54
feat: use Canonical JSON #612
feat: use Canonical JSON #612
Conversation
e126f10
to
e25ecd7
Compare
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.
LGTM (wich a couple of nits about package import order).
I seriously spent over an hour fixing package import order issues because of the linter. If we have some stated order, can you point me toward it? Because it appears that the order the linter expects is:
But it seems you are suggesting
And my understanding was that imports within those sections were to be in alphabetical order, which would have |
Now that we moved passed the order import kerfuffle, this is tied to cnabio/cnab-spec#73. Is there anything preventing the spec PR from getting merged? It also needs a rebase. |
This switches Duffle to use Canonical JSON, which provides JSON ordering that is conducive to hashing. http://wiki.laptop.org/go/Canonical_JSON This will increase interoperability with other languages and platforms, and match the ordering produced by security tools like Notary. Note that this change does not impact: - Claims (still stored as regular JSON) - Drivers (still receive regular JSON) - Repo (still uses regular JSON)
829f9ca
to
cee0aa9
Compare
Rebased. |
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.
LGTM
This switches Duffle to use Canonical JSON, which provides JSON ordering
that is conducive to hashing. http://wiki.laptop.org/go/Canonical_JSON
This will increase interoperability with other languages and platforms,
and match the ordering produced by security tools like Notary.
Note that this change does not impact: