leaysgur 5a73a663dc refactor(regular_expression)!: Simplify public APIs (#6262) ... This PR makes 2 changes to improve the existing API that are not very useful. - Remove `(Literal)Parser` and `FlagsParser` and their ASTs - Add `with_flags(flags_text)` helper to `ParserOptions` Here are the details. > Remove `(Literal)Parser` and `FlagsParser` and their ASTs Previously, the `oxc_regular_expression` crate exposed 3 parsers. - `(Literal)Parser`: assumes `/pattern/flags` format - `PatternParser`: assumes `pattern` part only - `FlagsParser`: assumes `flags` part only However, it turns out that in actual usecases, only the `PatternParser` is actually sufficient, as the pattern and flags are validated and sliced in advance on the `oxc_parser` side. The current usecase for `(Literal)Parser` is mostly for internal testing. There were also some misuses of `(Literal)Parser` that restore `format!("/{pattern}/{flags}")` back and use `(Literal)Parser`. Therefore, only `PatternParser` is now published, and unnecessary ASTs have been removed. (This also obsoletes #5592 .) > Added `with_flags(flags_text)` helper to `ParserOptions` Strictly speaking, there was a subtle difference between the "flag" strings that users were aware of and the "mode" recognised by the parser. Therefore, it was a common mistake to forget to enable `unicode_mode` when using the `v` flag. With this helper, crate users no longer need to distinguish between flags and modes.		2024-10-03 02:47:08 +00:00
..
parser.rs	refactor(parser): add --ast and --comments to example	2024-09-14 09:02:23 +08:00
parser_tsx.rs	docs(parser): add module and struct level documentation (#5831)	2024-09-18 06:27:24 +00:00
regular_expression.rs	refactor(regular_expression)!: Simplify public APIs (#6262)	2024-10-03 02:47:08 +00:00
visitor.rs	refactor(ast): pass final ScopeFlags into visit_function (#4283)	2024-07-16 07:22:07 +00:00