Re: [webauthn] Move `getAssertion()`'s `challenge` into `AssertionOptions`

I noted in https://github.com/w3c/webauthn/pull/398#issuecomment-293641860:
>> I'd be inclined to term [options] "params" or "parameters" but it is not a big deal

@mikewest replied:
> data or params or anything else is fine with me. I'm easy. :)
> How about AssertionRequest in 3a5fefb?

Well, in thinking about it let's leave that argument/parameter name as "options" -- "request", as attempted 3a5fefb, seems misleading because the dictionary semantically contains options/arguments/parameters and "options" is shorter. 

So going with the two commits -- https://github.com/w3c/webauthn/pull/398/commits/a9da99223c2da0bb07413af2d07b6aa36236421f and https://github.com/w3c/webauthn/pull/398/commits/0039a138e2d27567e7d32f0ddd203748bedb9cbb -- works for me. 




-- 
GitHub Notification of comment by equalsJeffH
Please view or discuss this issue at https://github.com/w3c/webauthn/pull/398#issuecomment-294038181 using your GitHub account

Received on Thursday, 13 April 2017 22:30:05 UTC