You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm submitting a possible bug report (excuse me if that's intentional and it's a feature request)
[X] bug report => Search github for a similar issue or PR before submitting
[ ] feature request => Please check if request is not on the roadmap already https://github.com/primefaces/primevue/wiki/Roadmap
[ ] support request => Please do not submit support request here, instead see http://forum.primefaces.org/viewforum.php?f=110
Current behavior
Currently, the Steps component does not support named routes, because of how it marks the active step:
What is the motivation / use case for changing the behavior?
Currently you need to duplicate your (possibly complex) routes in your router, as well as in your steps configuration. This is extremely painful when working with props:
I'm submitting a possible bug report (excuse me if that's intentional and it's a feature request)
Current behavior
Currently, the
Steps
component does not support named routes, because of how it marks the active step:https://github.com/primefaces/primevue/blob/master/src/components/steps/Steps.vue#L59
Expected behavior
I'd expect it to correctly mark routes as active even if I provide named ones:
What is the motivation / use case for changing the behavior?
Currently you need to duplicate your (possibly complex) routes in your router, as well as in your steps configuration. This is extremely painful when working with props:
The text was updated successfully, but these errors were encountered: