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
Since the release of 0.2.0, the following template variable names are reserved and managed by stakx.
this
site
data
collections
menu
pages
repeaters
PR #113 introduces a new redirects global variable, which could conflict with any existing templates that use redirects as a variable name; this is a huge problem for BC. How should this be handled?
Follow Jekyll and stuff everything into site
However, this poses the exact same problem but with site conflicting with configuration file keys.
Global variables are prefixed so they become stakx_site or stakx.site
Cross our fingers and hope no one complains or has used redirects as a variable name
The text was updated successfully, but these errors were encountered:
I think the second option is a good choice. Perhaps when an option is chosen instead of removing the old ones immediately, give a warning saying it will be removed in the next major release (with steps to fix it).
Since the release of 0.2.0, the following template variable names are reserved and managed by stakx.
this
site
data
collections
menu
pages
repeaters
PR #113 introduces a new
redirects
global variable, which could conflict with any existing templates that useredirects
as a variable name; this is a huge problem for BC. How should this be handled?site
site
conflicting with configuration file keys.stakx_site
orstakx.site
redirects
as a variable nameThe text was updated successfully, but these errors were encountered: