Show LCWIP fields in browse popups #498
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
Pete-Y-CS
approved these changes
Apr 8, 2024
|
Agreed it's confusing. Right now we have two sections of the popup. We could consolidate and have a way to indicate if that field is per-feature or per-scheme. Need to know how people want to use this. |
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.
A start towards #493. The extra LCWIP fields are invisible now; this at least starts showing them in per-feature popups. Also added bolding to values, to try and be consistent with the style for other browse popups.
I don't know if this way of presenting information is useful, but it seems better than not showing anything