Bug: Individual Summary entries get trimmed, instead of full collection.
#519
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
… records have more than 3.
erinesullivan
deleted the
bug-summarytruncate-applies-to-each-one-and-not-full-text
branch
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.
Overview
When viewing a
PrevieworMediumrecord, by default, each individual piece ofmetadatagets trimmed if the length of text goes beyond 240 characters. If a record has multiple summaries, each individual summary gets trimmed and displayed instead of being viewed as a whole block of text.To resolve this, the
metadataonly shows the first summary if not viewing aFullrecord, which gets trimmed if necessary.Testing