-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
File report on Enum values that ignore naming conventions in WebRTC E…
…ncoded Transform
- Loading branch information
1 parent
a208652
commit cbf259d
Showing
1 changed file
with
12 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
--- | ||
Title: Enum values that ignore naming conventions in WebRTC Encoded Transform | ||
Tracked: N/A | ||
Repo: 'https://github.com/w3c/webrtc-encoded-transform' | ||
--- | ||
|
||
While crawling [WebRTC Encoded Transform](https://w3c.github.io/webrtc-encoded-transform/), the following enum values were found to ignore naming conventions (lower case, hyphen separated words): | ||
* [ ] The value `"keyID"` of the enum `SFrameTransformErrorEventType` 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. | ||
|
||
<sub>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/).</sub> |