- From: Emil Lundberg via GitHub <sysbot+gh@w3.org>
- Date: Fri, 30 Aug 2024 12:45:15 +0000
- To: public-webauthn@w3.org
These enum values use a different naming convention because they are used as keys in the `record` returned by [`getClientCapabilities()`](https://w3c.github.io/webauthn/#sctn-getClientCapabilities). These names enable using them as bare identifiers (`capabilities.conditionalCreate` or `{ conditionalCreate: true }`) instead of having to use index notation (`capabilities["conditional-create"]`) or quoted keys (`{ "conditional-create": true }`).
The proposed naming convention was used at earlier points in #1923 but were later [changed to improve developer ergonomics](https://github.com/w3c/webauthn/pull/1923#pullrequestreview-1793420364).
--
GitHub Notification of comment by emlun
Please view or discuss this issue at https://github.com/w3c/webauthn/issues/2133#issuecomment-2321132318 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 30 August 2024 12:45:16 UTC