Update report on Enum values that ignore naming conventions in Web Authentication: An API for accessing Public Key Credentials - Level 3 #796
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request was automatically created by Strudy upon detecting errors in Enum values that ignore naming conventions in Web Authentication: An API for accessing Public Key Credentials - Level 3.
Similar errors had already been detected. Please check that the diff is correct, and that the errors have not already been reported in https://github.com/w3c/webauthn.
If everything is OK, you can merge this pull request which will report the issue below to the repo, and update the underlying report file with a link to the said issue.
Title: >-
Enum values that ignore naming conventions in Web Authentication: An API for
accessing Public Key Credentials - Level 3
Tracked: >-
Willfull design
w3c/webauthn#2133 (comment)
Repo: 'https://github.com/w3c/webauthn'
While crawling Web Authentication: An API for accessing Public Key Credentials - Level 3, the following enum values were found to ignore naming conventions (lower case, hyphen separated words):
"conditionalCreate"
of the enumClientCapability
does not match the expected conventions (lower case, hyphen separated words)"conditionalGet"
of the enumClientCapability
does not match the expected conventions (lower case, hyphen separated words)"hybridTransport"
of the enumClientCapability
does not match the expected conventions (lower case, hyphen separated words)"passkeyPlatformAuthenticator"
of the enumClientCapability
does not match the expected conventions (lower case, hyphen separated words)"userVerifyingPlatformAuthenticator"
of the enumClientCapability
does not match the expected conventions (lower case, hyphen separated words)"relatedOrigins"
of the enumClientCapability
does not match the expected conventions (lower case, hyphen separated words)"signalAllAcceptedCredentials"
of the enumClientCapability
does not match the expected conventions (lower case, hyphen separated words)"signalCurrentUserDetails"
of the enumClientCapability
does not match the expected conventions (lower case, hyphen separated words)"signalUnknownCredential"
of the enumClientCapability
does not match the expected conventions (lower case, hyphen separated words)See Use casing rules consistent with existing APIs in Web Platform Design Principles document for guidance.
This issue was detected and reported semi-automatically by Strudy based on data collected in webref.