-
-
Notifications
You must be signed in to change notification settings - Fork 367
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
fix: Collection page query over-fetching #11039
Conversation
✅ Deploy Preview for koda-canary ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Not sure if it's my network. It did not show the basic info about collection when I opened the link: ![]() |
@Jarsen136 it's weird on local it's working, checking |
@Jarsen136 fixed, can you check again |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
code lgtm
|
@Jarsen136 added #11055 in this pr -> 8a0cc9d that page is heavy so the issue might be that it takes a lot of time ( related with #10416 ) , it's working on my end , can you try again ? |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice
const route = useRoute() | ||
const collectionId = computed(() => route.params.id.toString()) | ||
|
||
const { collection, refetch } = useCollectionMinimal({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
collection
doesnt have proper types before. would be good if we can fix that here
PR Type
Context
get collection drops
api callsget collection drops
earlierExplore Algorithm
#11041Before
After
Screenshot 📸
Before
After