-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple BREAD for single table/model #5826
Comments
Depends on your needs of course. You can "fake" that with search filters. You might even be able to add mass action buttons instead of menu's, maintaining one "customers" menu with mass action shortcuts at the top. Create action buttons, with something like, probably better to use route keys, but for example.
You can make a mass action for each of your "filters" You can override the BREAD resources for that table and just build your own interface or lightly modify the existing one. ^ make your changes to that blade, point it at your own controller and do whatever you want. A hacky partial result would require you to remove the UNIQUE constraint on data_types.name, and then probably deal with other complications, like the listing not showing up in the bread list. You could potentially make models for each of the situations you need, but have them all point at the same database table. |
Laravel version
No response
PHP version
No response
Voyager version
No response
Description of problem
Is it possible for me to create multiple BREADs for one singular table?
Example:
One table named Customer
One BREAD where only shows Customer that is living in one state with use of scope
One BREAD where shows Customer that is living in another state with use of scope
One BREAD where shows Customer that is living in another different state with use of scope
The BREADs are created so admin can select on menu item where which state they want to view, such as choosing StateA on sidebar will lead to page where only shows StateA customers, StateB shows StateB customers and so on....
Or is there any other way to do this?
Proposed solution
Allow one database table/model to have multiple BREAD
Alternatives considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: