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
For the "Name/Value Pairs", using a prefix such as "t-" would safely namespace
these parameter names to allow future addition of properties without concerns
about clashing with deployed template parameters.
OK, this is a fair point about potential conflicts between template variables and current and future built-in parameters.
Do you suggest to prefix only in the application, so to "t-foo" would be actually interpreted as "foo" in the template, or to say that all template-defined variables must always start with "t-" prefix?
The text was updated successfully, but these errors were encountered:
OK, this is a fair point about potential conflicts between template variables and current and future built-in parameters.
Do you suggest to prefix only in the application, so to "t-foo" would be actually interpreted as "foo" in the template, or to say that all template-defined variables must always start with "t-" prefix?
The text was updated successfully, but these errors were encountered: