-
-
Notifications
You must be signed in to change notification settings - Fork 366
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
Infinite scroll for all views #2859
Conversation
✅ Deploy Preview for koda-nuxt ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Infinite scroll has been done in collection/{id}. @roiLeo |
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.
- why do you need a callback in
async fetchPageData
? - it is necessary to have a
loadDirection
? - can we try to use fetch hook?
- would be cool to add in a near future when there is "No Data" or the "End of Data", I think vue-infinite-slot provide slot template
Because it needs to notify the fetching status changed.
Yes, it is necessary to know in which direction will the paging data inserted.
Sorry but I still don't know the benefit if use
Yes, but let's finish the infinite scroll in all views first because there is still a lot of work to be done : ) |
Probably go on https://deploy-preview-2859--koda-nuxt.netlify.app/rmrk/explore?page=1 collections with small tiles as default? |
will check it later. |
|
Let's merge #2871 first, and then I could apply this fix to the other views and resolve conflicting code. |
Already modified code. Ready for code review now. |
first: this.first, | ||
offset: this.offset, | ||
} | ||
variables: { |
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.
Why u changed that from function to object?
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.
Because $apollo.query
need variables
to be an object.
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.
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.
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.
Both function
and object
could work.
However, the query does not need to be 'reactive' in this case.
So I use the object to be the param. 🤔
And if you have other reasons to use 'function', I could change it.
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.
I manage to break it? https://deploy-preview-2859--koda-nuxt.netlify.app/rmrk/collection/3892e43e923e5ad973-KAG?page=76 Another bug if I tried open this, did not load anything https://deploy-preview-2859--koda-nuxt.netlify.app/rmrk/collection/3892e43e923e5ad973-KAG?page=395 |
How is paging made? Because I scroll like 1-5 pixels vertically and change pages number pretty wild 😁 Screen.Recording.2022-04-27.at.14.16.04.mov |
oh, I will check it later. |
…-gallery into issue-1582-infinite-scroll
It is because the collection has only 26 pages of items, however the page number on the url is greater than this maximum. Let's see if your issue has been resolved now? @yangwao |
Seem the previous stuff has been fixed. Follow up issue could be
|
pay 300 usd |
😍 Perfect, I’ve sent the payout 🪅 Let’s grab another issue and get rewarded! |
Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR type
What's new?
Process:
test case: /rmrk/u/FZpjhYdt6fqRSzW1nR4fRejavcrSo7UXYP4TDhE3mgimgeC
Before submitting Pull Request, please make sure:
Optional
Had issue bounty label?
Community participation
Screenshot