Fix tree cell rendering #377
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
amolenaar
force-pushed
the
fix-tree-cell-rendering
branch
from
d39b2c3
to
dcc77cb
Compare
amolenaar
force-pushed
the
fix-tree-cell-rendering
branch
from
dcc77cb
to
a76a775
Compare
7 tasks
7 tasks
danyeaw
approved these changes
Jul 31, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Text in tree-view is misbehaving if you enter something between angular brackets, e.g.
Class<Type>Issue Number: #376
What is the new behavior?
You can enter those characters. Style (italic/bold) is set on cell level.
Does this PR introduce a breaking change?
Other information
Also fix rendering in diagram when you remove the name (e.g. for Classes)