Skip to content

Note non-anchoring of regexes in the regex section. #1297

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 4, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion jsonschema-core.xml
Original file line number Diff line number Diff line change
Expand Up @@ -563,6 +563,11 @@
These regular expressions SHOULD be valid according to the regular expression
dialect described in <xref target="ecma262">ECMA-262, section 21.2.1</xref>.
</t>
<t>
Unless otherwise specified by a keyword, regular expressions MUST NOT be
considered to be implicitly anchored at either end. All regular expression
keywords in this specification and its companion documents are un-anchored.
</t>
<t>
Regular expressions SHOULD be built with the "u" flag (or equivalent) to provide
Unicode support, or processed in such a way which provides Unicode support as
Expand Down Expand Up @@ -2441,7 +2446,8 @@
Validation succeeds if, for each instance name that matches any
regular expressions that appear as a property name in this keyword's value,
the child instance for that name successfully validates against each
schema that corresponds to a matching regular expression.
schema that corresponds to a matching regular expression. Recall: regular
expressions are not implicitly anchored.
</t>
<t>
The annotation result of this keyword is the set of instance
Expand Down