-
Notifications
You must be signed in to change notification settings - Fork 919
[POC] datatable as a component for multiple cruds #5688
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
Conversation
d84d59a to
65aa57b
Compare
39a4912 to
d8b8d16
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's
- Polish with the comments here.
- Set up a demo
- used a column in ShowOperation
- used as a widget in ShowOperation
- used in a dashboard as an x-component
| @endif | ||
| <x-datatable :crud="$crud" /> | ||
|
|
||
| </div> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Todo: let's write in the upgrade guide that the list.blade.php and datatables_logic.blade.php files have been turned into a datatable component - if they've made any changes to them, they can delete them from their project and re-do the changes in the component view (after publishing).
[ci skip] [skip ci]
[ci skip] [skip ci]
[ci skip] [skip ci]
…el-Backpack/CRUD into datatable-single-component
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.

This is a very early POC about something me and @tabacitu are exploring.
What we are trying to achieve here, can be summed up in the following way:
They way Backpack was built from start, although simple, comes with some limitations. Now that we want to introduce more advanced features we'd need to do major refactors of the software, that would take months for us to develop, and a lot of time for our users to upgrade.
We are always exploring the possibility of changing something internal that would allow us to do more advanced things, without the cost for the developers that use our software.
That said, one of the most requested features and needs we had, was to have a "relation table", without having to develop a new table from scratch, given how much effort we already spent on the Datatable/columns, and the huge amount of features we have on both of them.
Without much to add for the moment, we will need to decide on the direction we would like to take, here is a screenshot of somewhat we want to achieve:
All of that, with the simplicity we aim for our software:
At the moment there are 0 breaking changes, but also stuff that does no properly work. This is very very wip, we may find something that would require a major breaking change that we are not willing to do for the next version .. but it's a start. 👍