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 haven't tried changing it yet. I assume using normal string comparison is much faster - but some users may need localeCompare. Probably need an option to use one or the other based on if the user needs it - but I assume large percentage of users don't need localeCompare for routing.
Describe the bug
Matching a segment is taking ~45 ms due to localeCompare. This only happens when deep linking - the base route doesn't have an issue.
Your Example Website or App
https://lightning-js.github.io/solid-demo-app/#/browse/movie
Steps to Reproduce the Bug or Issue
Load up the site with 6x slowdown in Chrome - doing the initial match for a route takes ~45ms.
Expected behavior
Much faster matching of routes.
https://stackoverflow.com/questions/14677060/400x-sorting-speedup-by-switching-a-localecompareb-to-ab-1ab10
Recommend not using localeCompare
Screenshots or Videos
No response
Platform
Mac, Chrome, latest
Additional context
No response
The text was updated successfully, but these errors were encountered: