Fixing a couple of regressions (missing GraphQL fields). #2282
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.
Description
Both regressions affect the media card on the item page:
relationship.target.created_at
field, so we can fallback to it whenlast_seen
isnull
.relationship.target.requests_count
field, which is currently causing a "NaN Requests" error.Fixes: CV2-6126.
How to test?
Open any media cluster page that has more than one media.
Previously:
Now:
Checklist