v3.0.0

<a name"3.0.0">

3.0.0 (2016-12-06)

Bug Fixes

• ngTableColumn: setting column attribute fails (e532a4f4)
• ngTableColumnsBinding: cannot be used with ngTableDynamic directive (76c7396c)
• ngTableEventsChannel: event callbacks defines incorrect params (b7a2aa62)

Breaking Changes

• services and controllers now implemented using classes

This will only affect applications written in typescript

• renamed exported angular module: ngTable -> ngTableModule

Previously:

import { ngTable } from 'ng-table';

Now:

import { ngTableModule } from 'ng-table';

• ng-table/browser switched to using a named export for it's angular module

Previously:

import ngTableBrowserModule from 'ng-table/browser';

Now:

import { ngTableBrowserModule } from 'ng-table/browser';

• ng-table/core switched to using a named export for it's angular module

Previously:

import ngTableCoreModule from 'ng-table/core';

Now:

import { ngTableCoreModule } from 'ng-table/core';

• ngTableFilterRowController switched to use controllerAs

Practically this will only effect applications that:

1. have a custom directive that uses ngTableFilterRowController as it's controller
2. or have replaced the ngTable/filterRow.html template stored in the $templateCache

To upgrade, these applications will need to change their template to reference the controller
methods exposed on the $ctrl scope variable.

• ngTableGroupRowController switched to use controllerAs

Practically this will only effect applications that:

1. have a custom directive that uses ngTableGroupRowController as it's controller
2. or have replaced the ngTable/groupRow.html template stored in the $templateCache

To upgrade, these applications will need to change their template to reference the controller
methods exposed on the $ctrl scope variable.

• ngTableSorterRowController switched to use controllerAs

Practically this will only effect applications that:

1. have a custom directive that uses ngTableSorterRowController as it's controller
2. or have replaced the ngTable/sorterRow.html template stored in the $templateCache

To upgrade, these applications will need to change their template to reference the controller
methods exposed on the $ctrl scope variable.

• changed signatures of afterDataSorted + afterDataFiltered events

Previously:

(publisher: IDefaultGetData<T>, params: NgTableParams<T>, newData: DataResult<T>[] ): any

Now:

(publisher: NgTableParams<T>, newData: DataResult<T>[] ): any

(b7a2aa62)