You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding support for multiple partials directories will enable people to have their partials split across various directories. One common use-case is shared vs. server-only partials, where the shared partials are also used on the client, e.g., an app could have "shared/templates" and "views/partials" directories which contain templates that can be used as partials.
When naming the partials for use in other templates, each partials dir would be considered a root, therefore "views/partials/header.handlebars" would be available via {{> header}}. This creates a situation for naming collisions, which can be managed in a last-one-wins fashion.
The text was updated successfully, but these errors were encountered:
Adding support for multiple partials directories will enable people to have their partials split across various directories. One common use-case is shared vs. server-only partials, where the shared partials are also used on the client, e.g., an app could have
"shared/templates"
and"views/partials"
directories which contain templates that can be used as partials.When naming the partials for use in other templates, each partials dir would be considered a root, therefore
"views/partials/header.handlebars"
would be available via{{> header}}
. This creates a situation for naming collisions, which can be managed in a last-one-wins fashion.The text was updated successfully, but these errors were encountered: