-
Notifications
You must be signed in to change notification settings - Fork 987
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
A limit of 20 CryptoKitties is displayed in the collectibles list in the wallet with incorrect order #6839
Comments
Was not sure if this is a bug or a feature request, but according to the description in #5017 - it's a bug. |
it's a bug for sure, thank you |
@hetvart please add a test for this when you have time. This is definitely a regression |
I set it as the top priority task! |
Postponed it. Probably till I get an account with the needed amount of test collectibles. |
@asemiankevich did you test more than 20 CKs ? and it worked? |
i dont remember exactly how many kitties i did have once testing #5017. However now i have 23 kitties and only 20 is shown. |
i mean i'm not sure it's regression, i remember i didn't have more than 20 CKs, so i couldn't test properly |
wrong order is a regression anyway |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed. Please re-open if this issue is important to you. |
@rachelhamlin can we consider this? |
Adding to nice-to-have list, not blocker :) |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This issue now has a funding of 90.0 DAI (90.0 USD @ $1.0/DAI) attached to it.
|
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work has been started. These users each claimed they can complete the work by 2 weeks, 6 days from now. 1) samgos has started work. React is my bread to my butter and I'm able to read through other's code pretty well, let's give it a shot, will be done ASAP. Learn more on the Gitcoin Issue Details page. |
Welcome aboard @SamGos - you're doing to need to write Clojure and compile it to RN. Any Clojurescript familiarity? Here's our quickstart, just ping us with any questions, we're happy to help. |
Thank you for the approval, I will not let you down, Clojure no but the JVM yes. I'm sure I'll be fine, will do. |
Got the all the kitties showing, so now it's just a matter indexing them in the correct order, nearly there! |
Wow, awesome work @SamGos! Thanks for the update. |
I'm afraid I cannot find a viable solution for indexing the kitties correctly due to Clojure's abnormal behaviour when it comes to mapping and indexing values. Alongside working with
I have spent a surplus of 40 hours on this task, so it is no longer financially viable for me to continue. I'm sure you're developers could easily fix the sorting in a few minutes or perhaps give me some guidance, I would be more than happy to finish the job if so. I am not adept at Clojure and this is my first time using the language. Regardless I fixed the major problem of this issue I am just wondering am I still compliant for the reward. |
Opened a WIP PR at #9810, hopefully it may shine some light on how to implement the indexing. |
Thanks for the great effort @SamGos! I'll definitely compensate you for your time. |
That's awesome I'll submit the work on gitcoin then, forgive me for not sorting the indexing but at least the kitties are showing! |
Type: Bug
Summary: As a user, I would like to see the correct number of my collectibles in the wallet, in the right order.
Currently, only 20 CK are shown, without any option to show more of them.
As a user, I would be very confused
Expected behavior
The exact number of collectibles should be displayed in the correct order
Actual behavior
Only 20 CK are displayed in a different order from the App
Reproduction
Collectibles list, top of the list:
App list, top of the list:
Additional Information
Status version: 0.9.31 (1811211215); node 27700aa2 (Nov 22 nightly build)
Operating System: iOS, Android
The text was updated successfully, but these errors were encountered: