From 7b83697549a1a97c7e325d6a824e64dafd7a66b9 Mon Sep 17 00:00:00 2001 From: dontcallmedom-bot Date: Mon, 9 Sep 2024 12:29:00 +0200 Subject: [PATCH] File report on Enum values that ignore naming conventions in Web Cryptography API (#712) --- issues/WebCryptoAPI-wrongcaseenumvalue.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 issues/WebCryptoAPI-wrongcaseenumvalue.md diff --git a/issues/WebCryptoAPI-wrongcaseenumvalue.md b/issues/WebCryptoAPI-wrongcaseenumvalue.md new file mode 100644 index 00000000..07b2e6f2 --- /dev/null +++ b/issues/WebCryptoAPI-wrongcaseenumvalue.md @@ -0,0 +1,17 @@ +--- +Title: Enum values that ignore naming conventions in Web Cryptography API +Tracked: Widely deployed, unlikely to change at this point +Repo: 'https://github.com/w3c/webcrypto' +--- + +While crawling [Web Cryptography API](https://w3c.github.io/webcrypto/), 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](https://w3ctag.github.io/design-principles/#casing-rules) in Web Platform Design Principles document for guidance. + +Cc @dontcallmedom @tidoust + +This issue was detected and reported semi-automatically by [Strudy](https://github.com/w3c/strudy/) based on data collected in [webref](https://github.com/w3c/webref/).