nft-gallery
nft-gallery copied to clipboard
#3463 Master offers component
Thank you for your contribution to the KodaDot NFT gallery. π _ Let's make a quick check before the contribution.
PR type
- [ ] Bugfix
- [x] Feature
- [ ] Refactoring
What's new?
- [x] PR closes #3463
- [ ] Requires deployment <rubick/magick_issue>
- [x] route is
/bsx/offers
Before submitting Pull Request, please make sure:
- [x] My contribution builds clean without any errors or warnings
- [x] I've merged recent default branch -- main and I've no conflicts
- [x] I've tried to respect high code quality standards
- [x] I've didn't break any original functionality
- [x] I've posted a screenshot of demonstrated change in this PR
Optional
- [ ] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
- [ ] I've tested PR on mobile and everything seems works
- [ ] I found edge cases
- [ ] I've written some unit tests π§ͺ
Had issue bounty label?
- [x] Fill up your KSM address: Payout
Community participation
Screenshot
- [x] My fix has changed something on UI; a screenshot is best to understand changes for others.
SUCCESS @prachi00 PR for issue #3463 which is assigned to you. Please wait for review and don't hesitate to grab another issue in the meantime!
Deploy Preview for koda-nuxt ready!
Name | Link |
---|---|
Latest commit | 7f03f212413b875821958f5731e439027e1ceccc |
Latest deploy log | https://app.netlify.com/sites/koda-nuxt/deploys/6309eb1d46126e000a6ae253 |
Deploy Preview | https://deploy-preview-3692--koda-nuxt.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
tested without wallet logged in, received 400 network error, pls check
https://deploy-preview-3692--koda-nuxt.netlify.app
where? because if you are not logged in, then the option is hidden
So some feedback after checking this more thoroughly:
-
the tabs should be filter (F2) with two options as described in the issue, but let's make it three with first one being
All offers
, dropdown as the one for the offer status (F1). If there isn't valid address inserted, the F2 can be disabled dropdown (stuck atAll offers
), becoming enabled once there's valid address, giving two more filtering options, i.e.Offers Created
andIncoming Offers
-
logged out user should be able to land at this page, and still see all of the offers (without entering address), data should be fetched the same way as in
/bsx/stats
-
the entry field for address doesn't need
Check offers
button next to it, it could be 2 sec debounce and offers can be fetched once there's valid address
So some feedback after checking this more thoroughly:
- the tabs should be filter (F2) with two options as described in the issue, but let's make it three with first one being
All offers
, dropdown as the one for the offer status (F1). If there isn't valid address inserted, the F2 can be disabled dropdown (stuck atAll offers
), becoming enabled once there's valid address, giving two more filtering options, i.e.Offers Created
andIncoming Offers
- logged out user should be able to land at this page, and still see all of the offers (without entering address), data should be fetched the same way as in
/bsx/stats
- the entry field for address doesn't need
Check offers
button next to it, it could be 2 sec debounce and offers can be fetched once there's valid address
Regarding 2nd, can logged out users see the input box?
also initially, when the user reloads, there will be address in the input box and option will be all, so wouldn't it be confusing that what the address id doing?
can logged out users see the input box?
yes
also initially, when the user reloads, there will be address in the input box and option will be all, so wouldn't it be confusing that what the address id doing?
Hmm maybe we don't understand each other here, if there will be an address in the input field, you will be fetching all of the offers related to the address (incoming offers and made offers), if there isn't address, you're fetching all of the offers.
Also, if logged out users can see the input box, can they enter address and view incoming or created? because I was under the assumption that they cant do that
Also, if logged out users can see the input box, can they enter address and view incoming or created? because I was under the assumption that they cant do that
@petersopko β¬οΈ
Also, if logged out users can see the input box, can they enter address and view incoming or created? because I was under the assumption that they cant do that
yes, they can enter address and view incoming/created. input field is always enabled to enter an address, thing which is disabled is the filter until the valid address it's entered
@prachi00 any updates on this one? :)
@prachi00 any updates on this one? :)
sorry about the delay, I was out the whole last week but getting back to this from today
@petersopko initially when the user first opens it, should they see their own offers or general offers same as stats?
@petersopko initially when the user first opens it, should they see their own offers or general offers same as stats?
to quote from the initial issue description
When the logged-in user visits /bsx/offers it lands on its own address stats by default, i.e. in my case /bsx/offers?u=bXgvP2cQzEnPvuPQHRghz9dUYovqzyPhXBRXbNwVCef7nsmqb where default would be incoming offers
@petersopko fixed the issues mentioned
@petersopko fixed the issues mentioned
Test failed, and deepsource seems to have some kind of problem with the code tho ?
On mobile it looks like this
On mobile it looks like this
just merged with the main branch, should be fixed now
I have fixed the failing tests for you, please check this part of CONTRIBUTING.md for further reference on how to make the tests happy once you change some of the tested subjects :)
I have fixed the failing tests for you, please check this part of CONTRIBUTING.md for further reference on how to make the tests happy once you change some of the tested subjects :)
got it, thank you for fixing this time, I'll make sure to do it from next time
4. Offers
for 1 and 2, I actually depend on the url to fill out the address in the input
/bsx/offers?target=bXjGftu3aagU6RzMCKHi66X84jap3RKtvv6t1kxD2KXbJMiG2
because not doing this was creating a lot of edge cases for example, if you erase the input bar to view all the offers and then reload, it would show user's offers again
- Offers
for 1 and 2, I actually depend on the url to fill out the address in the input
/bsx/offers?target=bXjGftu3aagU6RzMCKHi66X84jap3RKtvv6t1kxD2KXbJMiG2
because not doing this was creating a lot of edge cases for example, if you erase the input bar to view all the offers and then reload, it would show user's offers again
@petersopko let me know if this seems okay to you?
let's resolve conflicts :)
let's resolve conflicts :)
done
Code Climate has analyzed commit 7f03f212 and detected 0 issues on this pull request.
View more on Code Climate.
@petersopko let me know if this seems okay to you?
it's not ideal, but this issue wasn't defined in great detail, so let's follow up with some tweaks
pay 150 usd
π Perfect, Iβve sent the payout π΅ $150 @ 45.38 USD/KSM ~ 3.305 $KSM π§ EzGc4s9PgCPx1YnF3fqzhLzVHpHMTL4LWPScwpDrR8JKgSU π 0x6ae7f9ab6b7fc3ea6a5dd18664c064f823e5b730ab15ec746513dc9f50c0c07b
πͺ Letβs grab another issue and get rewarded! πͺ github.com/kodadot/nft-gallery/issues