-
**Is your feature request related to a problem? Please describe.**
Unknown.
**Describe the solution you'd like**
can use as standard input pattern=`${regex}`
-
Merging #5256 provides support for optional parsed regex literals, We can enhance our regex-related linter rules to use this parsed pattern whenever available.
Here is the list of the rules operati…
-
**Describe the bug**
I don't see any real problem just noticed logs entries.
**Logs and dumps**
SecDebugLog & SecDebugLogLevel 3
```
[172440041140.141021]` [/vystrelovaci-rukavice-3-sipky/]…
-
I'm trying to filter some paths, where I want to use **. Unfortunately, the regex that's getting computed internal to `Glob::filter()` seems to be incorrect.
For example, the pattern `/**` compile…
Crell updated
4 weeks ago
-
### Clear and concise description of the problem
The typespec should add validation to `@pattern` or Azure specific linting rule for RegEx.
Recently we encountered an invalid [regex expression](…
-
@s-heppner mentioned in https://github.com/admin-shell-io/aas-specs/pull/426#issuecomment-2175441483 that zero is optional in regex quantifiers. I don't think that is true, at least in Java this doesn…
-
Hi,
Thanks for the amazing tool.
When I use regex patterns that start with a minus sign, it fails to recognize the pattern. I also tried escaping the minus with backslash and that it did not work …
-
**Is your feature request related to a problem? Please describe.**
Porting PCRE and Hyperscan regex patterns to NVIDIA Morpheus, existing solution uses functions from those frameworks that accept a re…
-
**Is your feature request related to a problem? Please describe.**
I want to exclude **/node_modules/** and **/.venv/** from my searches (installed libraries in software projects)
**Describe the s…
-
**Describe the bug**
If a file has the name `enums.py` anywhere in the repository, the `lint` goal for any linter that uses `LintFilesRequest` will run twice.
I was able to reproduce this in a cle…