-
-
Notifications
You must be signed in to change notification settings - Fork 378
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 linter messages in UI #4351
Conversation
tests fail 😅 |
Do we have to use markdown? Can't we just directly use HTML so we don't need an additional parser in the frontend? |
The error messages will also be used in CLI IIRC. So while the backticks also look ok on the CLI HTML does not. |
I would also like to avoid the possibility to inject complex HTML (classes etc.) from the backend in the frontend, so I think markdown supports basic formatting while we don't need to worry about injected HTML breaks the frontend formatting. But that might be my personal impression only. |
OK get your point, but I somehow worry about the size of the frontend as it increases and increases... Yes, probably this one is not the big problem but still it's better to use native features. |
Agree with that. What should we do in this particular case? IMO, properly formatting the linter messages in the UI is valuable and makes it more readable. |
d2ba381
to
575234c
Compare
The remaining test failure looks unrelated to my code changed? 🤔 Fixed by #4353 |
575234c
to
858c273
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4351 +/- ##
=======================================
Coverage 27.32% 27.32%
=======================================
Files 379 379
Lines 27757 27757
=======================================
Hits 7584 7584
Misses 19488 19488
Partials 685 685 ☔ View full report in Codecov by Sentry. |
Tearing down https://woodpecker-ci-woodpecker-pr-4351.surge.sh |
DocsLink
componentBefore:
After: