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
Is your feature request related to a problem? Please describe.
It is not easy to read stack traces in the current format.
Describe the solution you'd like
A "<code>" tag surrounding it or a special JS library like highlight.js or prismjs could solve this.
The text was updated successfully, but these errors were encountered:
lanzelot1989
changed the title
Use <code> tag or syntax highlighting JS library for stack traces in failure tab
[Feature] Use <code> tag or syntax highlighting JS library for stack traces in failure tab
Sep 10, 2018
lanzelot1989
changed the title
[Feature] Use <code> tag or syntax highlighting JS library for stack traces in failure tab
[Feature] Use <code> tag or syntax highlighting JS library for stack traces in failure tab
Sep 10, 2018
lanzelot1989
changed the title
[Feature] Use <code> tag or syntax highlighting JS library for stack traces in failure tab
[Feature] Use code-tag or syntax highlighting JS library for stack traces in failure tab
Sep 10, 2018
Is your feature request related to a problem? Please describe.
![image](https://user-images.githubusercontent.com/773651/45293533-ba94c080-b4f8-11e8-8095-aca234ba4f17.png)
It is not easy to read stack traces in the current format.
Describe the solution you'd like
![image](https://user-images.githubusercontent.com/773651/45293667-1c552a80-b4f9-11e8-8db4-07c424f3e91b.png)
A "<code>" tag surrounding it or a special JS library like highlight.js or prismjs could solve this.
The text was updated successfully, but these errors were encountered: