-
-
Notifications
You must be signed in to change notification settings - Fork 353
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: Current generative drops are not unlockable #7862
Conversation
✅ Deploy Preview for koda-canary ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
WARNING @Jarsen136 PR for issue #7843 which isn't assigned to you. Please be warned that this PR may get rejected if there's another assignee for issue #7843 |
AI-Generated Summary: This pull request addresses the issue with the current generative drops not being unlockable. The changes involve modifications in multiple files. A significant portion of code was removed, refactored, and consolidated into a new Vue component called The component is linked to the The |
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.
It looks like the api is checking if the nft is the unlockable item. Is there any idea to check if the collection is unlockable? @vikiival
#7843 (comment)
resolve/${prefix}-${nftId}
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.
@vikiival Could you please take a look at 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.
@vikiival Could you please take a look at it?
You have been pranked by bad naming
Usage of keywise is
const { isUnlockable, unlockLink } = useUnlockable(collection)
Therefore it is checking as
GET /resolve/${prefix}-${collectionId}
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.
LOL Thank you for pointing it out. I would correct the bad naming to avoid confusion.
Code Climate has analyzed commit bc14df8 and detected 0 issues on this pull request. View more on Code Climate. |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
KodaChain should be unlockable 🤔 |
what it should unlock? because for the waifu mints we unlock $ vouchers, but the kodachain we just give ppl the nft in case they voted for proposal |
Thanks! |
😍 Perfect, I’ve sent the payout 🪅 Let’s grab another issue and get rewarded! |
pay 30 usd |
😍 Perfect, I’ve sent the payout 🪅 Let’s grab another issue and get rewarded! |
Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type
Needs QA check
Context
Did your issue had any of the "$" label on it?
Screenshot 📸
Copilot Summary
🤖 Generated by Copilot at af98ea8
This pull request refactors the drop components to simplify their structure and extract common elements, such as the unlockable item info, into reusable components. It also introduces a new component
CollectionUnlockableItemInfo
that displays the unlockable content explanation based on the collection id. Additionally, it modifies theuseUnlockable
composable to accept a more generic type for the entity parameter. These changes improve the code readability, maintainability, and flexibility.🤖 Generated by Copilot at af98ea8