feat(frontend): collapse database_specific fields
#4194
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
Hmm... it looks a bit off. I was even thinking just have it like the affected versions above, and then collapsed by default. I think having too many sets of tabs could get confusing.
|
Hmm yes that looks completely broken. Last I tested it was supposed to look exactly like the affected versions, let me check that. |
@jess-lowe This is how it currently looks like on my end, also did a hard reload to make sure it's not cached. Could you confirm if it changes after a hard refresh maybe? |
|
Ok yes that fixed it. How weird! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Updates the
database_specificsection to collapse its top-level keys by default. Users can expand individual entries as needed, similar to how the "Affected versions" section works.Fixes #4163