Format type tables. #42
Merged
Conversation
This file contains hidden or 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
The JSON-like structures are more readable when formatted.
Attempt to improve readability by having entry options before entry type table data. Partly due to scrolling issues after the `<pre>` commit.
dlongley
approved these changes
Apr 2, 2025
Member
dlongley
left a comment
dlongley
left a comment
There was a problem hiding this comment.
This is a great UI improvement, thanks!
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.
<pre>formatting totypeTabledata for easier readability.typeTabledata cells to be wide, they were moved to the end so other columns easier to see.typeTabledata structures could be moved out into sections below the table itself, and have better scrolling. Scrolling the who table with anoverflow-x: scrollwrapper is not hard, but looked odd.Preview | Diff