esvit / ng-table / 701 / 1
95%
master: 93%

LAST BUILD BRANCH: strict-null-checks
DEFAULT BRANCH: master
Ran
Files 41
Run time 2s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 94.499%. Remained the same
701.1

push

travis-ci

ccrowhurstram 
refactor(ng-table): use of idomatic typescript

BREAKING CHANGES

* services and controllers now implemented using classes

This will only affect applications written in typescript

* renamed exported angular module: `ngTable` -> `ngTableModule`

Previously:

```js
import { ngTable } from 'ng-table';
```

Now:

```js
import { ngTableModule } from 'ng-table';
```

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

Previously:

```js
import ngTableBrowserModule from 'ng-table/browser';
```

Now:

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

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

Previously:

```js
import ngTableCoreModule from 'ng-table/core';
```

Now:

```js
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.

962 of 1018 relevant lines covered (94.5%)

339.97 hits per line

Source Files on job 701.1