Lazybones template for an AngularJs/Grails application
Groovy HTML CSS Shell
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
bin Build test apps first Aug 12, 2015
gradle/wrapper Fixing Book domain class. Updating Gradle version to 2.4 May 7, 2015
templates/angular-grails Using bower-installer and jasmine gradle plugins Aug 11, 2015
.gitignore Using bower-installer and jasmine gradle plugins Aug 11, 2015
README.adoc Update README.adoc Mar 31, 2015
build.gradle Adding circle.yml Aug 11, 2015
circle.yml Build test apps first Aug 12, 2015
gradlew.bat Initial commit Sep 23, 2014


Lazybones Template for AngularJS Grails


Getting started


You’ll need to have the following installed on your machine:

Creating a New Project

lazybones create angular-grails my-project

Running your project

Any new project makes use of the Grails Gradle plugin. You can start the application like this:

gradlew run

You can run all the tests (Groovy and Javascript) like this:

gradlew test

If you want to run just the Jasmine (JavaScript) tests use this command

gradlew jasmineRun

The following will run the Jasmine tests in watch mode (so that tests are rerun when your source changes):

gradlew jasmineWatch

Generate an AngularJS Module

CRUD Module

lazybones generate module

You can also avoid the prompts and set the properties directly:

lazybones generate module -PmoduleName=foo -PdomainClass=Foo

The above command will create a module with views, services, controllers, routes, etc. In the example above you can access your app by visiting /foo.

Blank Module

lazybones generate module::blank

You can also avoid the prompts and set the properties directly:

lazybones generate module::blank -PmoduleName=foo

The Grails PagedRestfulController

This is a modified version of the standard Grails RestfulController. It adds support for server side paging and filtering and can be used much like the RestfulController is used.

Here’s how you would add a REST controller for the Book domain class:

class BookController extends PagedRestfulController {
    BookController() {

It’s a good idea to override the default loadPagedResults method to be more selective about which fields (and how) you filter

class BookController extends PagedRestfulController {
    BookController() {

    protected PagedResultList loadPagedResults(params) {
        def filter = params.filter

        resource.createCriteria().list(max: params.max, offset: params.offset) {
            if (filter.title) {
                ilike('title', filter.title)
            if (filter.publishDate) {
                gt('publishDate', filter.publishDate)
            if (params.sort) {

Grails Plugins

This project makes use of the Asset Pipeline along with two AngularJs specific asset pipeline plugins that I developed:

The AngularJS grails module

This project includes an AngularJS module called grails that you can include as a dependency in your own angular modules.



This is a factory that you can use to create CrudResource object to help you make REST calls. This is essentially a wrapper for Angular’s own $resource module but the methods from a CrudResource object return a promise from all its methods and supports paging.

Here’s how you would create a CrudResource object

function AuthorResource(CrudResourceFactory) {
    // set the rest url and resource name here
    return CrudResourceFactory('/api/author', 'Author');

angular.module('', ['grailsCrud'])
    .factory('AuthorResource', AuthorResource);

Once you have a CrudResource object you can use it like this:

AuthorResource.list({page: 1}).then(function(items) {
  this.items = items;
  // items also has a getTotalCount function that provides the total item count for paging
  this.totalCount = items.getTotalCount();

// You can also pass a filter object for your controller to use
AuthorResource.list({page: 1, filter: {lastName: 'Burke'} }).then(function(items) {
  this.filteredItems = items;

AuthorResource.create().then(function(item) {
  this.newItem = item;

AuthorResource.get(1).then(function(item) {
  this.currentItem = item;

var item = {id: 1, title: 'Foo Bar'};


Each of the above functions can also accept an optional success and error callback function as the last two parameters:

var successFunction = function(response) {
    console.log("It worked!");

var errorFunction = function(response) {
    console.log("Uh oh!");

AuthorResource.delete(1, successFunction, errorFunction);


Used in conjunction with the flash-message directive below. This service allows you to easily set different messages in your app. Each time a flash message is set it overrides the previous one.

FlashService.success("Everything is fine");
FlashService.warning("Something bad is about to happen");
FlashService.error("Uh oh, something bad did happen");"Something good or bad might happen");
FlashService.clear(); // Clear message



This directive is used along with the FlashService above to display messages on the page.

<div flash-message></div>

The flash message template is located at: /grails-app/assets/vendor/grails/templates/directives/flash-message.tpl.html

sortHeader / sortableColumn

This directive allows you to keep track of the current sort state of a table, and has an onSort callback to allow you to reload your data if need be.

<thead sort-header ng-model="ctrl.sort" on-sort="ctrl.reloadData()">
    <th sortable-column title="Id" property="id"></th>
    <th sortable-column title="Name" property="name"></th>

The sortable column template is located at: /grails-app/assets/vendor/grails/templates/directives/sortable-column.tpl.html


This allows you to define a common template for your form fields (similar to the way the Fields plugin does with GSP pages). It includes a label, value and invalid property that are used within the template.

<form name="form" novalidate>
    <div field-container label="Title" value="ctrl.item.title" invalid="form.title.$invalid">
        <input name="title" ng-model="ctrl.item.title" required />

The fieldContainer template is located at: /grails-app/assets/vendor/grails/templates/directives/fields/field-container.tpl.html


Like the fieldContainer directive above, this defines a template for the displaying the field values (such as on a show page).

    <tr display-field label="Title" value="ctrl.item.title"></tr>

The displayField template is located at: /grails-app/assets/vendor/grails/templates/directives/fields/display-field.tpl.html


The click actions of these buttons are automatically set to make the appropriate method call from the default CrudResource. For example, clicking the delete button will call the DefaultResource.delete method.

<button crud-button="delete" item="ctrl.item" ></button>
<button crud-button="edit" item="ctrl.item" ></button>
<button crud-button="save" item="ctrl.item" ></button>
<button crud-button="create" ></button>

You can also include an optional afterAction parameter to register a callback or isDisabled to disable a button.

<button crud-button="delete" item="ctrl.item" after-action="ctrl.logDelete()"></button>
<button crud-button="save" item="ctrl.item" is-disabled="form.$invalid"></button>

The button templates are located at: /grails-app/assets/vendor/grails/templates/directives/buttons


This directive displays breadcrumb navigation for the different pages. The value can be set to list, create, edit or show.

<div crud-breadcrumbs="list" ></div>
<div crud-breadcrumbs="create" ></div>
<div crud-breadcrumbs="edit" ></div>
<div crud-breadcrumbs="show" ></div>

The breadcrumbs templates are located at: /grails-app/assets/vendor/grails/templates/directives/crud-breadcrumbs.tpl.html