This repository was archived by the owner on Apr 17, 2019. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 17, 2019. It is now read-only.
[META] Version 5 checklist #335
Description
This is a meta bug to show the current state of work for the future version of Datatable, Version 5.
If you have any questions or comments, please, make sure that you go to the particular issue/topic in question.
New Features
- Version 1.10 needs to be treated as a first class citizen. #333 - Version 1.10 needs to be treated as a first class citizen
- Allow setting all columns to be used for sorting #331 - Allow setting all columns to be used for sorting
- CollectionEngine does not support sorting by multiple columns at the same time #332 - CollectionEngine does not support sorting by multiple columns at the same time
- 'CustomEngine', an event based engine for searching #334 - 'CustomEngine', an event based engine for searching
Bug/Feature fixes
- Properly allow mocking Laravel for unit tests. #308 - Properly allow mocking Laravel for unit tests.
- Chumper/Datatable tests are broken #341 - Chumper/Datatable tests are broken
Activity
Chumper commentedon Oct 24, 2015
Hey @timgws, i could not find an email, so i just write a comment.
I have created a new branch
datatable3where i want to rewrite the plugin for laravel 5.I would like to invite you all to participate and discuss. A few ideas i already outlined there but there is definitely more stuff to discuss.
I also want to properly document every aspect of the plugin wherever possible, e.g. on an own page.
As you already did an awesome job on taking over the development i would be happy to have you on board for the new version.
Let me know what you think.
Javier-Rotelli commentedon Oct 26, 2015
hi @Chumper are you aiming for a complete rewrite?
I'm using this plugin on laravel 5 and it works great, it has bugs, but it mostly works.
I really like the idea of it having good documentation.
Chumper commentedon Oct 26, 2015
@Javier-Rotelli In most parts yes, but i am open to pull in already written code if it fits.
I want to clearly separate the three parts which are currently mixed together:
The current version was built with that in mind but as bugs came in I did not focus on that too much.
@timgws already started to work on some core components for a newer version and I would like to keep some of them in as he has the same idea in mind.