Josh-Cena
commented
1 year ago This information has almost nothing to do with the ES version; it's because the ES spec always refers to the latest Unicode spec, so as the Unicode spec upgrades, more property values are naturally supported. I'm not sure how we can best represent it—maybe we should have a separate entry called "Unicode version support", because Unicode version has other normative effects on ES behavior, see for example: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Lexical_grammar#white_space
robatwilliams
What type of issue is this?
Missing compatibility data
What information was incorrect, unhelpful, or incomplete?
There is a compatibility entry for these escapes at
javascript.regular_expressions.unicode_character_class_escape.That is a single entry, but successive ES versions have added more escapes. Examples can be found in the yearly rules of the eslint-plugin-es-x, such as es-x/no-regexp-unicode-property-escapes-2022.
It would be good to have the support for each different set of escapes be available in the database separately.
What browsers does this problem apply to, if applicable?
No response
What did you expect to see?
Database entries for
unicode_character_class_escape_2018,unicode_character_class_escape_2019, etc.Did you test this? If so, how?
Looked through database files, searched code and issues. Didn't find the information.
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_expressions/Unicode_property_escapes
Do you have anything more you want to share?
The lack of broken-down data by ES version/year is blocking https://github.com/robatwilliams/es-compat/issues/63
I'm not familiar with the use of these escapes, but it was @ota-meshi who implemented the detection rules in https://github.com/eslint-community/eslint-plugin-es-x/pull/26 and https://github.com/eslint-community/eslint-plugin-es-x/pull/65
MDN URL
No response
MDN metadata
No response