-
-
Notifications
You must be signed in to change notification settings - Fork 347
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
#4555 explore route changes #4577
Conversation
✅ Deploy Preview for koda-nuxt ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
https://deploy-preview-4577--koda-nuxt.netlify.app/bsx/explore/items?page=1 Seems this lines doesn't happen on |
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.
2 things:
- should we keep prefix in path? (
/${prefix}/explore/...
) I thought that it will be chainless - I don't see much difference in naming
items
vscollectibles
for me it mean the same thing. Can't we have something else?
It's possible to remove that blackout effect and render the component somehow without during switching tabs? Screen.Recording.2023-01-03.at.18.29.43.mov |
done |
Oh missed this one.
Right now, yes, keep it and another PR we will remove another as supabase endpoint is available, as I'm not sure if we will miss something or so, just one thing at time 🙏 😭
Let me visit library, I guess it depends on context, as more likely with artist items I would stick with collectibles, but having collectibles next to the collection sounds similar and visually not that distinguishing. So collections/items would be ok for now if we don't come something, could be separate issue later.
|
Screen.Recording.2023-01-04.at.13.20.23.mov
design https://user-images.githubusercontent.com/5887929/209315319-d2cd5a7e-c7db-49b4-852c-d28ce584e243.png |
Hey! example:
|
I heard whispers in cave something about supabase @vikiival We can disable them till now:) |
please, enlight us! |
does anyone know how to pass v-model as a prop in vue3, need it for the coomon tab component in libs, but unable to make it work, which is causing issues @roiLeo @preschian @Jarsen136 |
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.
- /explore throws 404
https://deploy-preview-4577--koda-nuxt.netlify.app/bsx/explore
components/shared/exploreTabsFilterSort/ExploreTabsFilterSort.vue
Outdated
Show resolved
Hide resolved
} | ||
</script> | ||
|
||
<style lang="scss"> |
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.
missing scoped?
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.
prachi00 marked this conversation as resolved.
components/shared/exploreTabsFilterSort/ExploreTabsFilterSort.vue
Outdated
Show resolved
Hide resolved
.explore-tabs { | ||
.btn-items { | ||
width: 240px; | ||
left: -6px; |
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.
I dont think there is any way to make the two buttons meet without any negative margin, since we are trying to make them look like tabs
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.
it wasn't working properly, so we decided to use buttons
CC @yangwao @preschian
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.
yes, this is because we are using a new layout. usually, the UI framework provides a button group. currently, oruga doesn't have that
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.
oruga doc
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.
TIL #4577 (comment), just read this message
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.
removed the negative margin
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.
Hey! why did you create a specific layout? I don't think it's needed from what I can see
@roiLeo so this was the approach I followed #4577 (comment) |
That's me the one who suggests using nested layouts. it should be easier if we use nested layouts in this case because the filter/sort button will be unified in the next iterate design. IMO profile/collection page should be using nested layouts also instead of tabs this is kinda similar to this https://beta.nextjs.org/docs/routing/pages-and-layouts#nesting-layouts |
I still don't understand the purpose but let's see.
so we'll create another layout? |
yes, IMO better to use a nested layout. please take a look at the attached image or this link https://nextjs.org/blog/layouts-rfc for the purposes in this picture, before next.js 13 support nested routes, usually I create multiple layouts to deliver the same goals with that https://constantsolutions.dk/2020/02/nested-layouts-in-nuxt-vue-js/ |
ok thanks for explenation I understand better we will use tabs as breadcrumb for explore pages |
Code Climate has analyzed commit b7570bd and detected 0 issues on this pull request. View more on Code Climate. |
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.
Haven't tested, code looks LGTM
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.
Hey, I'm happy we are closing on this, yet. I felt that, @prachi00, this issue was way too hard for you as the PR was opened over 2 weeks and accumulated a lot of comments and noise, which I don't prefer. Next time you should estimate if you are able to finish issue in short time. Let's say 2-3 days and not block others (issues) if they can take over? I really see it gets complex (34 files), yet it's better to leave room for others, we are playing on against time and distributing workload among other people :) |
pay 40 usd |
😍 Perfect, I’ve sent the payout 🪅 Let’s grab another issue and get rewarded! |
yeah I agree it did take time with reviews and stuff, as I had to migrate oruga tabs to a common component in library and use that, but then we decided to not use that and shift to buttons, so it did take time. I'll try to divide it into smaller tasks next time for sure. |
Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR Type
Context
Before submitting pull request, please make sure:
Optional
Had issue bounty label?
Payout
Community participation
Screenshot 📸