Skip to content

Commit

Permalink
Use v regexp flag
Browse files Browse the repository at this point in the history
  • Loading branch information
sisidovski committed Sep 13, 2023
1 parent d9af8a1 commit 27334d0
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions spec.bs
Original file line number Diff line number Diff line change
Expand Up @@ -423,8 +423,8 @@ A [=component=] has an associated <dfn for=component>group name list</dfn>, a [=
1. Let |part list| be the result of running [=parse a pattern string=] given |input|, |options|, and |encoding callback|.
1. Let (|regular expression string|, |name list|) be the result of running [=generate a regular expression and name list=] given |part list| and |options|.
1. Let |flags| be an empty string.
1. If |options|'s [=options/ignore case=] is true then set |flags| to "`ui`".
1. Otherwise set |flags| to "`u`"
1. If |options|'s [=options/ignore case=] is true then set |flags| to "`vi`".
1. Otherwise set |flags| to "`v`"
1. Let |regular expression| be [$RegExpCreate$](|regular expression string|, |flags|). If this throws an exception, catch it, and throw a {{TypeError}}.
<p class="note allow-2119">The specification uses regular expressions to perform all matching, but this is not required. Implementations are free to perform matching directly against the [=/part list=] when possible; e.g. when there are no custom regexp matching groups. If there are custom regular expressions, however, its important that they should be immediately evaluated in the [=compile a component=] algorithm so an error can be thrown if they are invalid.
1. Let |pattern string| be the result of running [=generate a pattern string=] given |part list| and |options|.
Expand Down

0 comments on commit 27334d0

Please sign in to comment.