Replies: 5 comments 5 replies
-
We support experimental decorators: https://biomejs.dev/reference/configuration/#javascriptparserunsafeparameterdecoratorsenabled :) |
Beta Was this translation helpful? Give feedback.
-
Ah just found it. TYVM. Just needed to add this!
|
Beta Was this translation helpful? Give feedback.
-
@1a35e1
Restarting the server does not fix anything: Restart LSP server form actions fix this issue for 1 second and then this error reappears. |
Beta Was this translation helpful? Give feedback.
-
I don't understand why this is closed sine WebStorm plugin still shows this false error. |
Beta Was this translation helpful? Give feedback.
-
To provide more context, the times it fails is when I have 2 or more projects open with different configurations. For example, is I have a NestJS project open and a React (vite) project open, one will fail. If NestJS project works correctly, the React project does not. If the React project works correctly, the decorator error show up. |
Beta Was this translation helpful? Give feedback.
-
Hi all,
Great tool, took it for a spin on a pretty large NestJS project. Given
experimentalDecorators
has been on the standards track for a while I can appreciate, why some this is not working 100% yet.In NestJS, its relatively common to have parameters injected in the
constructor()
or amethod()
It would be good if we could have a way to disable this warning/error while the API is in flux.
Currently I get
Decorators are not valid here.biome(parse)
which would be nice to ignore for now.Will be trying this on a ReactNative project next.
Thanks for the great work!
Beta Was this translation helpful? Give feedback.
All reactions