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
Thanks for the great work with Fractal - we've been investigating using it as a UI for the component library of an existing platform which already implements component identifiers containing forward-slashes e.g. module_foo/button. Unfortunately using this as a handle causes issues with routing and the following message is displayed when navigating to the preview:
"No matching route found for /components/detail/module_foo/button"
We're working around this currently using a build step to rewrite the forward slash but a possible solution might be to URL encode the handle when used for routing.
The text was updated successfully, but these errors were encountered:
Thanks for the great work with Fractal - we've been investigating using it as a UI for the component library of an existing platform which already implements component identifiers containing forward-slashes e.g.
module_foo/button
. Unfortunately using this as a handle causes issues with routing and the following message is displayed when navigating to the preview:"No matching route found for /components/detail/module_foo/button"
We're working around this currently using a build step to rewrite the forward slash but a possible solution might be to URL encode the handle when used for routing.
The text was updated successfully, but these errors were encountered: