This allows us to remove some of the “special” options (`format`, `context`, and `locals`) befor...

We had a “subtitle” local being passed to test plain strings being used as view parts, which isn...

Resolve methods from scope in order of data, context, partials

This reduces the risk of partials with names conflicting with data causing problems.

Support multiple template languages by inferring engine from template name

This change means we now support multiple template engines, and can do so without having to expl...

Make a shared context available across layouts, templates and partials

Replace parts with a single top-level scope

Rename layout parts and scope options

This makes the option clearer, since the scope in this case is _only_ applied to the layout, not...

As a name, "layout" seems more fitting and expected than "page", given there's no such concept a...

Unify handling of additional partial args and run through Part.build

Move all part construction logic into Part.build

This makes the controller’s job much simpler, and will make it possible to construct parts from ...

Make message for TemplateNotFoundError more readable

Allow falsey layout values to disable rendering of layout

Use exposures to prepare view locals

Instead, the input will go to the first argument provided it’s not already matching the name of ...

Just make it a little clearer we’re expecting to receive the proc as a normal argument, not ever...

This allows the API to be used in “method annotation”-style for all types of exosures, e.g.

exp...

This must’ve been a hangover from the original Rodakase project; we’re not using it here.

Rename layout to controller

It was never really clear how this could be helpful in a realistic scenario, so let’s deemphasis...

“name” made sense when this part of a Dry::View::Layout class, but now that it’s called Dry::Vie...

This is the first step in reorienting people’s approach to dry-view. Since the main job of Dry::...

Make arguments to partial method calls available within their templates

Support multiple template paths

Rack >= 2.0.0 requires Ruby >= 2.2.0, and we still support older versions of Ruby here.

Fix error: Template file is not valid US-ASCII

Related to: https://github.com/hanami/view/issues/76

Render template content before rendering layout content

This allows for content sharing from the template up to the layout. For example, via a “content_...

Use a part object as the layout template's scope

This should allow rendering of partials via `== partial_name` instead of having to chain them on...