-
Notifications
You must be signed in to change notification settings - Fork 15
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
CodeAction to disable validation #531
Comments
Fixes redhat-developer#531 Signed-off-by: azerr <azerr@redhat.com>
See redhat-developer/quarkus-ls#531 Signed-off-by: azerr <azerr@redhat.com>
Fixes redhat-developer#531 Signed-off-by: azerr <azerr@redhat.com>
See redhat-developer/quarkus-ls#531 Signed-off-by: azerr <azerr@redhat.com>
Fixes redhat-developer#531 Signed-off-by: azerr <azerr@redhat.com>
Fixes redhat-developer#531 Signed-off-by: azerr <azerr@redhat.com>
See redhat-developer/quarkus-ls#531 Signed-off-by: azerr <azerr@redhat.com>
Fixes redhat-developer#531 Signed-off-by: azerr <azerr@redhat.com>
Fixes redhat-developer#531 Signed-off-by: azerr <azerr@redhat.com>
Fixes redhat-developer#531 Signed-off-by: azerr <azerr@redhat.com>
Fixes #531 Signed-off-by: azerr <azerr@redhat.com>
See redhat-developer/quarkus-ls#531 Signed-off-by: azerr <azerr@redhat.com>
I reopen the issue because we need to manage code action to disable validation but for a given file. @fbricon have you some idea about the settings name that we can use it to define a set of templates. A quick idea "quarkus.tools.qute.validation.excluded" : [
"*.items.qute.html"
"*.book.qute.*"
] It's simple but not powerfull (ex : we cannot configure some severity fo some error code for a given set of files). @fbricon what do you think? |
It's good enough. |
Ok thanks. I will implement it. The idea is to have 2 code actions:
I wonder if we need a code action like |
keep it simple for now, just this file pattern. |
Fixed by #535 |
When there is an error in qute template it should be nice to provide a code action to disable validation in other words update the proper validation settings like we do for application.properties validation.
When validation settings severity for each error code will be implemented it should be nice to provide an another code action to disable the settings for the given error code.
The text was updated successfully, but these errors were encountered: