Route overrides
Last updated
Last updated
This is the official documentation of the forestadmin/laravel-forestadmin
v2+ and forestadmin/symfony-forestadmin
PHP agents.
Route overrides ↗ allowed customizing the behavior of the routes exposed by the agent.
This very low-level feature was used to implement many use cases:
Attach handlers to events in the UI
Customize filtering, search and sort behaviors
Other advanced use cases.
Because our new agent API is higher-level, the protocol used to communicate between the agent and the application can no longer be manipulated.
What was the route override used for? | How to migrate it? |
---|---|
Custom permissions would better be implemented by using the Roles ↗ feature from the UI.
Define a new route into your web.php
file:
Add a new method into your Controller.
Add custom permissions
Use .addHook() and throw forbidden errors
Add validation to fields
Use .addFieldValidation() instead
Add validation to whole records
Use .addHook() and throw validation errors
Run code on UI events
Use .addHook() to perform custom logic
Change the search behavior
Use .replaceSearch() to implement your custom search logic
Change the filtering behavior of fields
Change the sort behavior of fields
Other use case
If you are stuck or think that this guide can be improved, please expose your use case in the community forums ↗ and we will be happy to help you