This repository was archived by the owner on May 26, 2023. It is now read-only.
Refactor data-viewer to rely on css not js, improve UX #142
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What
Data-Viewer component now processes ellipsis using CSS instead of JS
Add ability to set the number of lines you want to view in preview of data-viewer (ie. when not expanded)
Change "Expand" arrow to appear on hovering over the element
Set max width to 60% of the screen
Why
Allows to properly truncate text when changing the window width
Improves performance on large amount of data
Better "Expand" arrow UX