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

feat: extract non cacheable fields out of grid items #11093

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

MounirDhahri
Copy link
Member

This PR resolves []

Description

PR Checklist

  • I have tested my changes on iOS and Android.
  • I hid my changes behind a feature flag, or they don't need one.
  • I have included screenshots or videos, or I have not changed the UI.
  • I have added tests, or my changes don't require any.
  • I added an app state migration, or my changes do not require one.
  • I have documented any follow-up work that this PR will require, or it does not require any.
  • I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

  • I would like at least one of the reviewers to run this PR on the simulator or device.
Changelog updates

Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

  • extract non cacheable fields out of grid items - mounir

Need help with something? Have a look at our docs, or get in touch with us.

@MounirDhahri MounirDhahri self-assigned this Nov 13, 2024
@MounirDhahri MounirDhahri marked this pull request as draft November 13, 2024 14:38
import { useEffect, useState } from "react"
import { fetchQuery, graphql } from "react-relay"

export const fetchArtworkNonCacheableFields = async (artworkID: string) => {
Copy link
Contributor

Choose a reason for hiding this comment

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

I understand the quick win here but I think we could follow Force's approach https://github.com/artsy/force/pull/14533/files#diff-5a8e92cd05a6757b15a42e921874b7ab7ff1fc4471985e2736ff02525a8724adR163

fetchQuery definition points out of using it outside of React, so inside React elements we should aim for splitting the smaller parts into standalone query elements like @mzikherman did in the PR

Copy link
Member Author

Choose a reason for hiding this comment

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

your comment makes sense. I don't remember why I've done it that way actually.
Anyway, I am not happy with both approaches because both would lead to n queries for each grid and I want to investigate ways to avoid that.

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