Grio and Angular 2: Are They Ready for Each Other?


At Grio, we love Angular.  By my estimation we currently use it for at least half of our front-end web application code.  And I in particular have affection for it, so I greeted the recent release of Angular2 with some interest and trepidation.

The release was just an event, though. The framework had already been around long enough for me to fret about it for some time.

Server-side pagination with AngularJS


AngularJS is one of the most used Javascript frameworks nowadays.

A characteristic of this framework is the possibility of binding input or output parts of an HTML page to a model represented by standard JavaScript variables.

Looping through arrays and collections is made easy by the ngRepeat directive.
This directive becomes handy when dealing with lists and tables, especially if associated to the AngularJS filters, which allow you to handle pagination, filtering and sorting by adding just one line of code to your html.

Unfortunately, one of the limitations of this approach is that the filtering is done client-side, therefore it wouldn’t be an optimal solution when dealing with a substantial number of rows/records.