-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Improve errors reporting of QuteProcessor #25724
Labels
Milestone
Comments
Hm, the build output is primarily intended for developers not IDEs... so it should be concise but also readable. That said, we could improve the current message. @angelozerr How about something along these lines?
|
mkouba
added a commit
to mkouba/quarkus
that referenced
this issue
May 26, 2022
mkouba
added a commit
to mkouba/quarkus
that referenced
this issue
May 26, 2022
mkouba
added a commit
to mkouba/quarkus
that referenced
this issue
May 26, 2022
mkouba
added a commit
to mkouba/quarkus
that referenced
this issue
Jun 9, 2022
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Jun 13, 2022
- resolves quarkusio#25724 (cherry picked from commit 46bfea0)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Description
When a quarkus application is build (with native or not), the step
io.quarkus.qute.deployment.QuteProcessor#processTemplateErrors
is very verbose and for IDE / Editor it is hard to capture those errors to display them in the IDE / Editors:Here a sample of error:
Implementation ideas
It should be really nice to simplify the error reporting like https://code.visualstudio.com/docs/editor/tasks#_defining-a-problem-matcher to have an error per line:
The previous sample generate an error like this:
helloWorld.c:5:3: warning: implicit declaration of function ‘prinft’
For Qute error, it could be become:
Instead of having:
The text was updated successfully, but these errors were encountered: