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
Why consolidate so much logic for handling data instead of just a navigation library? Apis that solve real problems in the project are not provided (e.g., how do I get the last route path? How to navigate in non-React components). It's laced with a lot of apis that you don't really need in your work. Putting data processing logic inside routes is confusing.
Using the results returned by createHashRouter for navigation will inevitably lead to circular dependencies.
v6 simply removed 'path-to-regexp'. Why not let the user choose whether they want to use 'path-to-regexp'? If library users are willing to bear the size of 'path-to-regexp'.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Why consolidate so much logic for handling data instead of just a navigation library? Apis that solve real problems in the project are not provided (e.g., how do I get the last route path? How to navigate in non-React components). It's laced with a lot of apis that you don't really need in your work. Putting data processing logic inside routes is confusing.
Using the results returned by createHashRouter for navigation will inevitably lead to circular dependencies.
v6 simply removed 'path-to-regexp'. Why not let the user choose whether they want to use 'path-to-regexp'? If library users are willing to bear the size of 'path-to-regexp'.
Beta Was this translation helpful? Give feedback.
All reactions