-
Couldn't load subscription status.
- Fork 100
feat: impl Soft Binding assertion definition #1147
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
Conversation
cca0a83 to
d189d86
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.
We need unit tests for this as well as some level of integration test to show how it would be used in practice.
…nick/soft-binding
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 think this is ready to go but I'd like to not add the practice of appending Map to field names unless our plan is to do that everywhere, and I'm not sure what it adds.
… suffix from related structs
* feat: impl Soft Binding assertion definition * fix: remove `AssertionJson` impl for `SoftBinding` * fix: use usize for timespan * docs: clarify `alg_params` field string type * style: move soft binding pad fields to the bottom of struct * fix: soft binding region field optional and add unit + integration tests * fix: clippy lints * fix: use u64 instead of usize for soft binding time range * fix: hide and skip serializing deprecated soft binding fields and expose accessor * test: ignore deprecated url field in soft binding serialization test * docs: document deprecated methods and remove assertion creation version * refactor: move SoftBinding::pad/pad2 fields as methods and remove Map suffix from related structs * fix: `SoftBinding::alg_params`->`SoftBinding::alg-params` w/ serde --------- Co-authored-by: Eric Scouten <scouten@adobe.com> Co-authored-by: Gavin Peacock <gpeacock@adobe.com>
Changes in this pull request
Implements the Soft Binding assertion definition. It exposes all public fields so it's clear in the docs how to deserialize into it and it provides no functions since everything is already accessible by field. Getters/setters can be added on if wanted, but there is already a lot of variation in the implementation of assertions.
Checklist
TO DOitems (or similar) have been entered as GitHub issues and the link to that issue has been included in a comment.