-
-
Notifications
You must be signed in to change notification settings - Fork 532
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
💅 matching $ unsupported in naming convention due to Anchor assumption #5173
Comments
Have you tried escaping the $ like this? |
Yes I have tried to escape using I have also tried to get around it fully by using |
No, I meant with only one |
Yeah that is resulting in an
|
Interesting. There must be something going wrong because we explicitly allow
But the diagnostic you're seeing seeing seems to becoming from the JSON parser, not the rule or |
@jstephens986 can you please update the playground:
So we can reproduce the diagnostics you're seeing |
cc @Conaclos Maybe he can help us |
Environment information
Rule name
linter/style/useNamingConvention
Playground link
https://biomejs.dev/playground/?code=YwBvAG4AcwB0ACAAdABhAGIAbABlAEMAbwBsAHUAbQBuAFcAaQBkAHQAaABTAHQAeQBsAGUAcwAgAD0AIABjAHMAcwA8AHsACgAgACAAJABjAG8AbAB1AG0AbgBTAGkAegBlAD8AOgAgAG4AdQBtAGIAZQByAAoAIAAgACQAdABhAGIAbABlAFMAaQB6AGUAOgAgAG4AdQBtAGIAZQByAAoAfQA%2BAAoACgAgACAALwAvACAAIAAgACAAIAAgACAAIgB1AHMAZQBOAGEAbQBpAG4AZwBDAG8AbgB2AGUAbgB0AGkAbwBuACIAOgAgAHsACgAgACAALwAvACAAIAAgACAAIAAgACAAIAAgACIAbABlAHYAZQBsACIAOgAgACIAdwBhAHIAbgAiACwACgAgACAALwAvACAAIAAgACAAIAAgACAAIAAgACIAbwBwAHQAaQBvAG4AcwAiADoAIAB7AAoAIAAgAC8ALwAgACAAIAAgACAAIAAgACAAIAAgACAAIgBzAHQAcgBpAGMAdABDAGEAcwBlACIAOgAgAGYAYQBsAHMAZQAsAAoAIAAgAC8ALwAgACAAIAAgACAAIAAgACAAIAAgACAAIgBjAG8AbgB2AGUAbgB0AGkAbwBuAHMAIgA6ACAAWwAKACAAIAAvAC8AIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAB7AAoAIAAgAC8ALwAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAiAHMAZQBsAGUAYwB0AG8AcgAiADoAIAB7ACAAIgBrAGkAbgBkACIAOgAgACIAdAB5AHAAZQBQAHIAbwBwAGUAcgB0AHkAIgAgAH0ALAAKACAAIAAvAC8AIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIgBtAGEAdABjAGgAIgA6ACAAIgAoAFwAXAAkACkAPwAoAF8AKQA%2FAFsAYQAtAHoAQQAtAFoAXwAwAC0AOQBdACsAIgAKACAAIAAvAC8AIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAB9ACwACgAgACAALwAvACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAewAKACAAIAAvAC8AIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIgBzAGUAbABlAGMAdABvAHIAIgA6ACAAewAgACIAawBpAG4AZAAiADoAIAAiAG8AYgBqAGUAYwB0AEwAaQB0AGUAcgBhAGwAUAByAG8AcABlAHIAdAB5ACIAIAB9ACwACgAgACAALwAvACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACIAbQBhAHQAYwBoACIAOgAgACIAKABcAFwAJAApAD8AKABfACkAPwBbAGEALQB6AEEALQBaAF8AMAAtADkAXQArACIACgAgACAALwAvACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAfQAsAAoAIAAgAC8ALwAgACAAIAAgACAAIAAgACAAIAAgACAAXQAKACAAIAAvAC8AIAAgACAAIAAgACAAIAAgACAAfQAKACAAIAAvAC8AIAAgACAAIAAgACAAIAB9AA%3D%3D
Expected result
I am encountering an issue with styled-components where certain properties can be prefixed with
$
to make them transient. However, when attempting to create a namingConvention rule to target these properties, the Biomejs configuration becomes invalid. This appears to be due to an incorrect assumption that all$
characters are expression anchors in the Biomejs config.It is expected that tailing
$
only be counted as an anchors.Code of Conduct
The text was updated successfully, but these errors were encountered: