Introduced Lotus::View::Configuration with a bare minimum behavior
Make CI to depend on 'lotus/utils' HEAD
Implemented Lotus::View::Configuration#load_paths
Implemented Lotus::View::Configuration#layout
Removed Lotus::View's class accessor for layout, in favor of the API of Lotus::View::Configuration
Removed Lotus::View's class accessor for root, in favor of the API of Lotus::View::Configuration
Implemented Lotus::View::Configuration#views and #layouts
Lotus::View can be safely duplicated. Moved views and layout registries into Configuration. Configuration is now able to duplicated and (un)load itself. Layouts can be looked up in a given Ruby namespace.
Temporary add a .gitkeep to make the build to pass again
Lazily load layout for Configuration. This mechanism solves eventual race conditions between the loading of the framework and the application.
Ensure independent configurations between the framework, the views and its children. Lotus::View::Dsl.root now internally uses the configuration.
Ensure to return the correct template name for namespaced views
Make the tests compatible with the newest Utils::LoatPaths API
Specify different scenario for template name in a standalone application
Ensure lazy loading and correct namespace of the layout class when using configuration's "layout" DSL
Introducing Lotus::View.generate as shortcut for .duplicate and .configure