-
Notifications
You must be signed in to change notification settings - Fork 172
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
Strongly type client extension inputs and outputs #765
Strongly type client extension inputs and outputs #765
Conversation
The type |
The |
@agl can you please approve this PR now that the unused typedef has been removed? Thanks. |
index.bs
Outdated
:: Returns a JSON array of 3-element arrays of numbers that encodes the factors in the authenticator extension output. | ||
<xmp class="idl"> | ||
typedef sequence<unsigned long> uvmEntry; | ||
typedef sequence<uvmEntry> uvmEntries; |
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.
Nit: Should these typedefs' names also have initial uppercase like the others?
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.
Done. Thanks for the careful read @emlun .
I concur with agl, this looks good to me as well. |
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.
Looks good to me.
Client extension inputs and outputs are now strongly typed. Several individual extensions were also cleaned up so that their JavaScript and CBOR representations directly correspond to one another. The example extension was so irregular and ad-hoc as to actually be a terrible example. It was therefore deleted. The existing extensions now should serve as good examples.
Fixes #346
Fixes #626
Partially fixes #713
Partially fixes #738
Preview | Diff