solitary-daze

Changes:

Tested ng2-md-datatable with @angular/material 2.0.0-beta.6, now the peer dependency is just "@angular/material ~2.0.0-beta" to work with any beta version of @angular/material.

chimichurri-ui

Fixes:

• improved rendering on mobile devices
• improved pagination rendering (discussed here: #44)

twin-arrows

Fixes:

• streamlined events order to prevent UI inconsistencies (using queue/trampoline Rx.Scheduler)
• Adjusted style of sort arrows to match https://material.io/guidelines/components/data-tables.html#data-tables-specs

async-tote

Fixes:

• Applied some optimizations to datatable’s events and the way they are propagated to EventEmitters, with regards of Angular’s change detection. To solve some UI glitches still ocurring sometimes during change detection on my main app.

boring-release

Fixes:

• Nothing really exciting, fixed a minor cosmetic issue where the ”check all” checkbox would stay checked even after the table has redrawn with no element.

reduxtastic

Fixes:

• Fixed that MdDataTableComponent would emit one IDatatableSelectionEvent and one IDatatableSortEvent just after mounting. You probably don't need to capture the initial value using these EventEmitters, and just want to listen for changes when the user interacts with the MdDataTableComponent.

News:

• The library now hooks to the Redux DevTools Chrome Extension if present. It's mainly useful for the library maintainers, not much for the library users. But feel free to install this Chrome extension to monitor the DataTable's store state. Also don't expect to have fancy features like time travel or actions reorder to work, I've just implemented a basic monitoring of actions and state.

dizzy-rocksteady

Fixes:

• Fixed build pipeline of this library, I hope it is now "state of the art".
• Migrated CircleCI configuration to v2.0 for using a docker image.

Breaking Changes:

• There should not be (and I still recommend using Angular 4.x and Angular CLI 1.0 with this lib).

Known issues:

• none (unless your feedback?)

Contributing:

• Feel free to open PR to enhance this project!
• I'll put very thin guidelines, basically in order to have a good PR merged:
  • please run gulp lint before opening a PR to make sure it complies to the current tslint.json / stylelint.json
  • please double-check that the build status of your branch is passing on CircleCI
  • feel free to write some unit or protractor tests, they are always welcome!

amnesia-fix

News:

• Fixed a re-rendering bug when the content of datatable gets updated by an Observable.
• I've added a "Shuffle" button in the demo-app to demo such change.
• Added CircleCI configuration, build, and badges in README.

Breaking Changes:

• Removed deprecated MdDatatable.forRoot(), please use MdDatatable instead.

Known issues:

• AOT compilation using angular-cli fails. This may be linked to my current build pipeline and/or Angular-CLI itself. For some reasons the binaries in dist/ are missing some important decorators (are they tree-shaked?). Consequently, my client app is complaining about @NgModule missing on MdDatatableModule, for instance. Any help would be appreciated to solve this, thanks :)
• Note that it also happens in 1.3.2, but 1.3.1 was apparently okay.

aldous-harvest

News:

• This version is compatible with Angular 4.x and Material 2-beta.3
• Column headers use the proper material arrow icon (thanks @Raphyyy)
• Fixed weird selection behavior when sorting columns (rows will now be deselected)

Breaking Changes:

• This version can be used with Angular 4.x only. For Angular 2.4.x you may use versions 1.2.x.

maintenance-mint

News:

• Ditched @ngrx/store to use my own implementation, so as to not wait for their upgrades for upgrading my lib to the next Angular versions.
• Fixed gulp tasks gulp lint, gulp test and gulp publish
• Moved demo-app into src/demo-app

Breaking Changes:

• MdDataTableModule.forRoot() will be deprecated at some point, hence I recommend just importing MdDataTableModule instead.

Known issues:

• Currently unable to compile AOT with Angular-CLI 1.0, I suspect that something is broken on their side. [UPDATE]: Actually this shall be fixed with this version.
• Not yet compatible with Angular 4.x (but soon).