Mojolicious-Plugin-Branding

 view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

0.004  2026-10-26 09:13:24 CET
   - BREAKING: the "brand" helper returns the controller when setting
     the brand, so that calls can be chained, e.g.
     $c->brand('acme')->render(...).
   - BREAKING: unknown keys in the configuration and in "individual"
     make the plugin croak, e.g. "paths" from versions before 0.003.
   - BREAKING: a brand set to undef removes the brand configured by an
     earlier registration, instead of being skipped.
   - Roles are applied to the application's renderer and static file
     server, and the "brand" helper is added, only when "individual"
     has a "stash_key" or names a brand; global-only configurations
     leave them alone.
   - A valid configuration no longer triggers $SIG{__DIE__} handlers.
   - The template cache of each brand has the same class as the
     application's one, instead of always being a Mojo::Cache.
   - Errors about invalid paths say where they are, e.g.
     "(brand 'acme', public)" or "(global)".
   - An invalid configuration leaves the application untouched:
     "global" directories are only added once the whole configuration
     is valid.

0.003  2026-10-26 00:32:17 CET
   - BREAKING: individual brands are configured with "brands", a hash
     from brand names to their directories, instead of "paths"; brand
     names no longer come from directory names. A brand can also have
     separate "templates" and "public" directories, and
     "ignore_app_paths" to stop falling back to the application.
   - BREAKING: "stash_key" defaults to "branding.brand" instead of
     "variant". Brand and variant are now independent: application
     variants keep working for branded requests, brands can have their
     own variant templates, and templates/index.html+acme.ep is no
     longer used for brand "acme".



( run in 1.147 second using v1.01-cache-2.11-cpan-1bcd28dbaf1 )