Replies: 2 comments 7 replies
-
Hi, thanks for raising this. In Filament, we automatically register routes for you. In many cases, these route names are dynamic and generated by the framework. They can also change between minor releases. As such, Filament doesn't have a backwards compatibility promise on route names, since they can change. Because we don't ensure BC, I don't think anyone should be referencing Filament route names in their projects. the As such, I don't see much point in allowing customisation of these things. What are your thoughts? |
Beta Was this translation helpful? Give feedback.
-
Hi, I came across a requirement where I need to reference the panel's name in some logics. In a healthcare management system I have separate dashboard for Doctors, Staff, Vendor etc. Based on the role(s) I need switch/redirect them. Currently I am using hardcoded urls for these. Thanks |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Atm filament hardcoded the route name prefix with
filament
filament/packages/panels/routes/web.php
Line 11 in a1b7f45
Hi @danharrin hope you are doing well, just wondering, will filament team consider allowing us to configure it via config?
Sample use case: 1 single laravel app, 1 main panel, all pages use filament, then to simplify routes, strip all prefix on route path and route name.
Current
route:list
And possibly also configure panel route name prefix here as well (instead of using panelId):
filament/packages/panels/routes/web.php
Line 25 in a1b7f45
Ideal
route:list
Hope this make sense, but if this is not possible, no worries, just drop/close this, thanks!
Not sure if this is related to #12446, but seems unresolved.
Beta Was this translation helpful? Give feedback.
All reactions