All template handling is async by default. Instead of adding .compileSync, we felt that it made more sense to add .compileAsync, since .compile is a public method and most users will expect it to be sync, and .compile methods with most engines are typically sync. In other words, .compileAsync probably won't be seen by most users, but we wanted to explain the decision to go against node.js naming conventions.
Improved layout detection and handling

0.12.0

published 0.12.0 • 9 years ago

Changelog

Adds helper methods, .hasAsyncHelper, .hasHelper, .getAsyncHelper, and .getHelper
Ensures that both collection and app routes are handled when both are defined for a view

0.11.4

published 0.11.4 • 9 years ago

published 0.11.3 • 9 years ago

published 0.11.2 • 9 years ago

published 0.11.1 • 9 years ago

published 0.11.0 • 9 years ago

Changelog

Default engine can now be defined on app or a collection using using app.option('engine'), views.option('engine')
Default layout can now defined using app.option('layout'), views.option('layout'). No changes have been made to view.layout, it should work as before. Resolves issue/#818
Improves logic for finding a layout, this should make layouts easier to define and find going forward.
The built-in view helper has been refactored completely. The helper is now async and renders the view before returning its content.
Adds isApp, isViews, isCollection, isList, isView, isGroup, and isItem static methods. All return true when the given value is an instance of the respective class.
Adds deleteItem method to List and Collection, and deleteView method to Views.
Last, the static _.proto property which is only exposed for unit tests was renamed to _.plugin.