This post is a followup to Part 1 - Getting Started, so if you haven’t already created an application using the Angular Grails Lazybones template, you should probably start there.
Now I’m going talk about the ways you can further customize and tailor the Angular modules that the lazybones template generates.
Whenever you run the lazybones generate module command, it references the files found in src/templates/angular/crud in your main project to build out your new module:
The files here mirror your project structure, so you have fine grain control over what files are created and where they ultimately end up.
Any files with a .gtpl extension will be processed by the Groovy’s SimpleTemplateEngine so the rules about escaping characters apply here.
You can use the variables DOLLAR_SIGN, TAB, and NEWLINE within your template files so to add those characters without having to worry about escaping them.
You’ll notice in the screenshot above, that certain folder and file names have values like _resourceName_ or _groupPath_. These refer to values that allow you to have more control over the destination of your template files. Note the use of the underscores surrounding the variable names in the file/folder names.
Here’s a list of the variables that can be used to help build the paths within your project:
|groupPath||Java source path based on your project group||com/craigburke/angular (for group com.craigburke.angular)|
|resourceName||The domain class name||Employee|
|moduleName||the angular module name||exampleApp.employee|
|modulePath||Path based on angular module name||example-app/employee (for module exampleApp.employee)|
In addition to the path variables above, a map of variable for each domain property are add as a variable properties
|name||The property name||birthDate|
|label||The natural name based on the property name||Birth Date|
|type||The class of the property||java.util.Date|
|domainClass||Boolean indicating whether the property is a domain class||false|
|constraints||A map of the constaints for the property||[required: true, nullable: false]|
So given our example domain class Employee:
The properties variable would have this value within your templates
This takes into account the Grails default of properties being required and non-nullable when determining the constraints.
The RenderUtil class is an easy way to expose new methods or properties to your templates. You can also override any of the variables listed above if you’d like.
Any property or closure assigned to the util map within this file will be available within your templates.
As an example, here’s how I could expose a new method called renderPanel within my templates:
These added properties or methods can be used in any of the files found in your template folder (not just HTML files). The HTML files are just where I found these additional methods most useful (using them almost like Grails TagLibs).
I wanted to provide a good starter project for anyone looking to use Grails and AngularJS together but I also wanted to make it easy to configure any aspect of the project.
I’m looking forward to hearing how people are making use of this or if anyone has suggestions. I’m going to use this template extensively in my own work and will continue to work actively on it, so as always feedback is definitely welcome.