Skip to content
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

Merged
merged 27 commits into from
Jan 13, 2023
Merged

#4555 explore route changes #4577

merged 27 commits into from
Jan 13, 2023

Conversation

prachi00
Copy link
Member

@prachi00 prachi00 commented Dec 28, 2022

Thank you for your contribution to the KodaDot NFT gallery.

👇 _ Let's make a quick check before the contribution.

PR Type

  • Bugfix
  • Feature
  • Refactoring

Context

Before submitting pull request, please make sure:

  • My contribution builds clean without any errors or warnings
  • I've merged recent default branch -- main and I've no conflicts
  • I've tried to respect high code quality standards
  • I've didn't break any original functionality
  • I've posted a screenshot of demonstrated change in this PR

Optional

  • I've tested it at </bsx/collection>
  • I've tested PR on mobile
  • I've written unit tests 🧪
  • I've found edge cases

Had issue bounty label?

  • Fill up your KSM address:
    Payout

Community participation

Screenshot 📸

  • My fix has changed something on UI; a screenshot is best to understand changes for others.
    Screen Shot 2022-12-28 at 2 37 55 PM

@prachi00 prachi00 requested a review from a team as a code owner December 28, 2022 22:40
@prachi00 prachi00 requested review from roiLeo and removed request for a team December 28, 2022 22:40
@netlify
Copy link

netlify bot commented Dec 28, 2022

Deploy Preview for koda-nuxt ready!

Name Link
🔨 Latest commit b7570bd
🔍 Latest deploy log https://app.netlify.com/sites/koda-nuxt/deploys/63c0d6902bfc360009d30d76
😎 Deploy Preview https://deploy-preview-4577--koda-nuxt.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@kodabot
Copy link
Collaborator

kodabot commented Dec 28, 2022

WARNING @prachi00 PR for issue #4555 which isn't assigned to you. Please be warned that this PR may get rejected if there's another assignee for issue #4555

@prachi00 prachi00 changed the title Feat explore route #4555 explore route changes Dec 28, 2022
@prachi00
Copy link
Member Author

@yangwao
Copy link
Member

yangwao commented Jan 1, 2023

https://deploy-preview-4577--koda-nuxt.netlify.app/bsx/explore/items?page=1

Seems this lines doesn't happen on main branch

image

@yangwao yangwao added the S-changes-requested-🤞 PR is almost good to go, just some fine tunning label Jan 1, 2023
Copy link
Contributor

@roiLeo roiLeo left a 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 vs collectibles for me it mean the same thing. Can't we have something else?

components/rmrk/ExploreLayout/ExploreLayout.vue Outdated Show resolved Hide resolved
pages/_prefix/explore/items.vue Outdated Show resolved Hide resolved
components/rmrk/ExploreLayout/ExploreLayout.vue Outdated Show resolved Hide resolved
@yangwao
Copy link
Member

yangwao commented Jan 3, 2023

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

@prachi00
Copy link
Member Author

prachi00 commented Jan 4, 2023

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

@yangwao
Copy link
Member

yangwao commented Jan 4, 2023

Oh missed this one.

should we keep prefix in path? (/${prefix}/explore/...) I thought that it will be chainless

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 🙏 😭

I don't see much difference in naming items vs collectibles for me it mean the same thing.

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.

image

Can't we have something else?

@yangwao
Copy link
Member

yangwao commented Jan 4, 2023

done

  • Seems black transition is back on second time?
  • Tab states are not reflecting where the user wants to go and return me back?
Screen.Recording.2023-01-04.at.13.20.23.mov

image

  • Let's make it "Collections" and "Items" for now :)
  • Plus the tick symbol missing?

design https://user-images.githubusercontent.com/5887929/209315319-d2cd5a7e-c7db-49b4-852c-d28ce584e243.png

@roiLeo
Copy link
Contributor

roiLeo commented Jan 4, 2023

Hey!
How to distinguish filters by chain?

example:

  • Most Emoted on rmrk
  • Most Offers on bsx

@yangwao
Copy link
Member

yangwao commented Jan 4, 2023

How to distinguish filters by chain?

I heard whispers in cave something about supabase @vikiival

We can disable them till now:)

@roiLeo
Copy link
Contributor

roiLeo commented Jan 4, 2023

I heard whispers in cave something about supabase @vikiival

please, enlight us!

index

@prachi00
Copy link
Member Author

prachi00 commented Jan 5, 2023

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

@prachi00
Copy link
Member Author

prachi00 commented Jan 5, 2023

To explain more:
Screen Shot 2023-01-04 at 7 40 11 PM
we have this in explore component, I want the v-model to be passed to NeoTab and in turn call the getter and setter when it changes, but it is not happening

Copy link
Member

@vikiival vikiival left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

}
</script>

<style lang="scss">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

missing scoped?

Copy link
Member

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.

.explore-tabs {
.btn-items {
width: 240px;
left: -6px;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🙅

Copy link
Member Author

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

Copy link
Contributor

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,

bulma doc, buefy doc

since we are trying to make them look like tabs

why don't we use tab?

Copy link
Member Author

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

Copy link
Member

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

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oruga doc

Copy link
Member

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

@prachi00 maybe try with the bulma approach that @roiLeo sent the link

Copy link
Member

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

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed the negative margin

layouts/explore-layout.vue Outdated Show resolved Hide resolved
@yangwao yangwao removed the S-code-lgtm-✅ code review guild has reviewed this PR and it's code is approved label Jan 11, 2023
Copy link
Contributor

@roiLeo roiLeo left a 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

@prachi00
Copy link
Member Author

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)

@preschian
Copy link
Member

preschian commented Jan 12, 2023

Hey! why did you create a specific layout? I don't think it's needed from what I can see

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

@roiLeo
Copy link
Contributor

roiLeo commented Jan 12, 2023

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.

I still don't understand the purpose but let's see.
Remember that we'll have different sorting option from chain

IMO profile/collection page should be using nested layouts also instead of tabs

so we'll create another layout?

@preschian
Copy link
Member

I still don't understand the purpose but let's see.
Remember that we'll have different sorting option from chain
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, <Header />, <Footer />, and <DashboardSidebar /> are on the layout. in our case <DashboardSidebar /> === <SortFilter />. why did we put that component in the layout? because when we navigate to Collectibles/Item the content only changes on the dashed area (see the 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/

image

@roiLeo
Copy link
Contributor

roiLeo commented Jan 12, 2023

ok thanks for explenation I understand better we will use tabs as breadcrumb for explore pages

@codeclimate
Copy link

codeclimate bot commented Jan 13, 2023

Code Climate has analyzed commit b7570bd and detected 0 issues on this pull request.

View more on Code Climate.

Copy link
Member

@vikiival vikiival left a 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

Copy link
Contributor

@roiLeo roiLeo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ it looks good!

Collection

Screenshot 2023-01-13 at 15-08-52 Low minting fees and carbonless NFTs KodaDot - Kusama NFT Market Explorer

Gallery

Screenshot 2023-01-13 at 15-08-24 Low minting fees and carbonless NFTs KodaDot - Kusama NFT Market Explorer

But mobile is not very optimal yet

Screenshot 2023-01-13 at 15-10-52 Low minting fees and carbonless NFTs KodaDot - Kusama NFT Market Explorer

We can expand this in another issue

Note

  • mobile design need some love
  • border changes on pagination is done on purpuse?
  • find a bug when on /rmrk/explore/items & click "Collections" in navbar, then view is updating but not the tab

@yangwao
Copy link
Member

yangwao commented Jan 13, 2023

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?
It's OK to make follow-up issue; commit what you have. Making it longer for the same payout won't help. I value if things are getting closed FAST. I'll probably write you on Discord to talk more about this :)

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 :)


image
image

@yangwao
Copy link
Member

yangwao commented Jan 13, 2023

pay 40 usd

@yangwao
Copy link
Member

yangwao commented Jan 13, 2023

😍 Perfect, I’ve sent the payout
💵 $40 @ 27.74 USD/KSM ~ 1.442 $KSM
🧗 EzGc4s9PgCPx1YnF3fqzhLzVHpHMTL4LWPScwpDrR8JKgSU
🔗 0x661034be70b5488286137dcf16cfdd1f0f09bb77cc574d0f87ed850da55f9b03

🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues

@yangwao yangwao added the paid pull-request has been paid label Jan 13, 2023
@yangwao yangwao merged commit 7a4d4c3 into main Jan 13, 2023
@yangwao yangwao deleted the feat-explore-route branch January 13, 2023 14:27
@prachi00
Copy link
Member Author

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? It's OK to make follow-up issue; commit what you have. Making it longer for the same payout won't help. I value if things are getting closed FAST. I'll probably write you on Discord to talk more about this :)

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 :)

image image

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
paid pull-request has been paid S-changes-requested-🤞 PR is almost good to go, just some fine tunning S-visual-ok-✅
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Explorer Tabs bar
7 participants