Closed DarkGhostHunter closed 1 month ago
The latest updates on your projects. Learn more about Vercel for Git βοΈ
Name | Status | Preview | Updated (UTC) |
---|---|---|---|
ui | β Failed (Inspect) | Dec 28, 2023 4:52pm |
@DarkGhostHunter Thanks for this PR! Don't you think it would be better to call this component USteps
?
Also, would it make sense to support links?
@DarkGhostHunter Thanks for this PR! Don't you think it would be better to call this component
USteps
?
Yep, that's okay.
I thought of a ULadder
because you go up and down step by step. Also UStairs
for the same reason.
Also, would it make sense to support links?
Well, it does with to
, but only if you click the icon.
Its tricky to support links because the link would:
So I went with the easy route only supporting the click on the icon. Now that you mention it, I should add a hover effect.
As previous attempts show, creating this type of element is tricky and doesn't come without its own limitations and issues, primarily because the design of the step and the separators themselves. Some concessions on functionality and design must be made to avoid unwanted or shallow behavior.
I've encountered this issue on the Breadcrumb
component and added the divider outside of the link: https://github.com/nuxt/ui/blob/dev/src/runtime/components/navigation/Breadcrumb.vue#L24
Also, it would be nice to move this component to the Navigation
category π
I've encountered this issue on the
Breadcrumb
component and added the divider outside of the link: https://github.com/nuxt/ui/blob/dev/src/runtime/components/navigation/Breadcrumb.vue#L24
Yeah, but here the separstor would be tricky to put unless...
...we add four separators. Two each side of the icon, and two each side of the whole step. This way the looks like the separators are one.
To align them, we should use a 3x2 CSS grid instead, that way the separators on the top can be naturally aligned in the center of the first row, where the icon is.
Also, it would be nice to move this component to the
Navigation
category π
Go ahead.
@DarkGhostHunter Do you plan to keep working this PR or should I take over?
You may take over. The time I had left to work on it is gone π₯
Any news?
Hey ! Is there any news on this PR ? Thanks :)
I haven't found the time to finish this unfortunately. I think this will be dropped and implemented in v3
(#1289) later on as a feature request has been opened in Radix Vue: https://github.com/radix-vue/radix-vue/issues/805.
I haven't found the time to finish this unfortunately. I think this will be dropped and implemented in
v3
(#1289) later on as a feature request has been opened in Radix Vue: radix-vue/radix-vue#805.
Me neither. I have some nitpicks about the implementation, but either way it's better to wait for radix, or push a PR there.
π Linked issue
Resolves #180
β Type of change
π Description
This is my interpretation of #549. While is not that simplier like the aforementioned, it's more flexible in design:
While I tried to make it vertically compatible, it's impossible without making spaghetti code to support both orientations. Instead, we should grab inspiration from Tailwind UI Feeds.
π Checklist