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
Background: I've worked on a syntax-highlighter which adds a for each section of text that's colored differently.
As key, I use the index of the element, it's format name and the actual content of the element.
The content can contain whitespaces or blank lines. It can also be very long strings.
How often does this bug happen?
Every time
DevTools package (automated)
No response
DevTools version (automated)
No response
Error message (automated)
No response
Error call stack (automated)
No response
Error component stack (automated)
No response
GitHub query string (automated)
No response
The text was updated successfully, but these errors were encountered:
It looks like you forgot to specify a valid URL. (This means that we will not be able to reproduce the problem you're reporting.)
Please help us by providing a link to a CodeSandbox (https://codesandbox.io/s/new), a repository on GitHub, or a minimal code example that reproduces the problem. (Screenshots or videos can also be helpful if they help provide context on how to repro the bug.)
JannikGM
changed the title
[DevTools Bug]: Newline in component key string will look odd in component view
[DevTools Bug]: Newline in component key string will look odd in component tree
May 3, 2024
Website or app
/
Repro steps
Create an element with a key like
Foo\n\n\n\nBar\n\n\n\nBaz
and it will occupy multiple lines in the component tab.Here's a screenshot:
Background: I've worked on a syntax-highlighter which adds a for each section of text that's colored differently.
As key, I use the index of the element, it's format name and the actual content of the element.
The content can contain whitespaces or blank lines. It can also be very long strings.
How often does this bug happen?
Every time
DevTools package (automated)
No response
DevTools version (automated)
No response
Error message (automated)
No response
Error call stack (automated)
No response
Error component stack (automated)
No response
GitHub query string (automated)
No response
The text was updated successfully, but these errors were encountered: