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

> I'd be inclined to term it "params" or "parameters" but it is not a big deal

`data` or `params` or anything else is fine with me. I'm easy. :)

> My recollection is that we had kept the challenge separate from the truly optional options because the challenge is a must-have.

As I'm sure you noted, the `challenge` is marked as `required`, so this will throw a `TypeError` if it's not present on the dictionary that's passed in. I think the guarantees are much the same as the existing code.

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

Received on Wednesday, 12 April 2017 16:56:13 UTC