Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixing a couple of regressions (missing GraphQL fields). #2282

Merged
merged 1 commit into from
Feb 6, 2025

Conversation

caiosba
Copy link
Contributor

@caiosba caiosba commented Feb 6, 2025

Description

Both regressions affect the media card on the item page:

  • Request the relationship.target.created_at field, so we can fallback to it when last_seen is null.
  • Request the 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:

Captura de tela de 2025-02-06 00-14-09

Now:

Captura de tela de 2025-02-06 00-50-17

Checklist

Both regressions affect the media card on the item page:

* Request the `relationship.target.created_at` field, so we can fallback to it when `last_seen` is `null`.
* Request the `relationship.target.requests_count` field, which is currently causing a "NaN Requests" error.

Fixes: CV2-6126.
@caiosba caiosba merged commit 5127753 into develop Feb 6, 2025
11 checks passed
@caiosba caiosba deleted the fix/CV2-6126-nan-requests branch February 6, 2025 05:01
@caiosba
Copy link
Contributor Author

caiosba commented Feb 6, 2025

Reviewers, I merged because it was an urgent fix for live... but please review!

Copy link
Contributor

@sarahkeh sarahkeh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@caiosba
Copy link
Contributor Author

caiosba commented Feb 6, 2025

Thanks Sarah! I'm going to deploy to live now.

caiosba added a commit that referenced this pull request Feb 6, 2025
Both regressions affect the media card on the item page:

* Request the `relationship.target.created_at` field, so we can fallback to it when `last_seen` is `null`.
* Request the `relationship.target.requests_count` field, which is currently causing a "NaN Requests" error.

Fixes: CV2-6126.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants