File report on Enum values that ignore naming conventions in Web Cryptography API

[dontcallmedom-bot]

This pull request was automatically created by Strudy upon detecting errors in Enum values that ignore naming conventions in Web Cryptography API.

Please check that these errors were correctly detected, and that they have not already been reported in https://github.com/w3c/webcrypto.

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 Cryptography API
Tracked: N/A
Repo: 'https://github.com/w3c/webcrypto'

While crawling Web Cryptography API, the following enum values were found to ignore naming conventions (lower case, hyphen separated words):

• The value "deriveKey" of the enum KeyUsage does not match the expected conventions (lower case, hyphen separated words)
• The value "deriveBits" of the enum KeyUsage does not match the expected conventions (lower case, hyphen separated words)
• The value "wrapKey" of the enum KeyUsage does not match the expected conventions (lower case, hyphen separated words)
• The value "unwrapKey" of the enum KeyUsage 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.}

[tidoust]

I added the "Cc" paragraph to hopefully avoid it being raised another time!