You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of this commit, notifications cannot be rendered using any form of newline supported by markdown. As all HTML tags, including <br> are removed (sensible for preventing any XSS attacks) and all '\n' are removed, no way of defining newlines in markdown can be used anymore. This behavior is the same in VSCode, but highly requested to change there as well (see their issue #101589).
I would specifically like this feature to be able to show exception traces generated on a server application to the user. Those notifications are currently being butchered as all formatting for the stack trace is removed.
Other than aligning with VSCode, is there any specific reason to not support newlines in the notifications? Or is there some way around this to still be able to configure the notifications to allow for newlines?
The text was updated successfully, but these errors were encountered:
Other than aligning with VSCode, is there any specific reason to not support newlines in the notifications?
The main reason is to align with vscode, and have a consistent representation of newlines in standard notifications.
Please note that it is possible to use modal notifications to render newlines if needed: #7500.
I would specifically like this feature to be able to show exception traces generated on a server application to the user.
I do not believe the framework wants to deviate from vscode at this time and have an inconsistent behavior when displaying messages. If and when #101589 has been implemented we can re-work the current default implementation.
Or is there some way around this to still be able to configure the notifications to allow for newlines?
The framework provides a default implementation, it is always possible for downstream application developers to define their own custom @theia/ extensions which extend/override the default implementation to suit their needs and use-cases. In this case, you can extend the implementation for notifications to support markdown and/or newlines.
Feature Description:
As of this commit, notifications cannot be rendered using any form of newline supported by markdown. As all HTML tags, including
<br>
are removed (sensible for preventing any XSS attacks) and all'\n'
are removed, no way of defining newlines in markdown can be used anymore. This behavior is the same in VSCode, but highly requested to change there as well (see their issue #101589).I would specifically like this feature to be able to show exception traces generated on a server application to the user. Those notifications are currently being butchered as all formatting for the stack trace is removed.
Other than aligning with VSCode, is there any specific reason to not support newlines in the notifications? Or is there some way around this to still be able to configure the notifications to allow for newlines?
The text was updated successfully, but these errors were encountered: