As of Civi 5.71 (https://github.com/civicrm/civicrm-core/pull/29187), the smarty-v2 mixin has a new name: smarty. Because... it's not necessarily Smarty v2. Both names will continue to work in the same way. However, we should start encouraging the new name.
Before
Whenever civix activates Smarty support, it uses smarty-v2@1.x.x.
After
Whenever civix activates Smarty support, it checks the compatibility (eg <ver>5.50</ver> or <ver>5.75</ver>). If the target is 5.71+, then it will prefer the new name.
Comments
There's a trade-off in how one does this:
We could do a straight rule to switch all ext's to smarty@. This will push the newer name sooner... but you're more likely to get backport files (mixin/smarty@1.0.0.mixin.php)
We could do a conditional rule (smarty2@ if less than <ver>5.71</ver>; andsmarty@ for newer). Then it'll take a bit longer to push folks to the new name smarty@... but you don't get as many files.
TBH, I think both problems are superficial, and I don't think it really matters. My guess is that we'd get more pushback about extra-files than about the old-name, so that's what this PR does.
Overview
As of Civi 5.71 (https://github.com/civicrm/civicrm-core/pull/29187), the
smarty-v2
mixin has a new name:smarty
. Because... it's not necessarily Smarty v2. Both names will continue to work in the same way. However, we should start encouraging the new name.Before
Whenever
civix
activates Smarty support, it usessmarty-v2@1.x.x
.After
Whenever
civix
activates Smarty support, it checks the compatibility (eg<ver>5.50</ver>
or<ver>5.75</ver>
). If the target is 5.71+, then it will prefer the new name.Comments
There's a trade-off in how one does this:
smarty@
. This will push the newer name sooner... but you're more likely to get backport files (mixin/smarty@1.0.0.mixin.php
)smarty2@
if less than<ver>5.71</ver>
; andsmarty@
for newer). Then it'll take a bit longer to push folks to the new namesmarty@
... but you don't get as many files.TBH, I think both problems are superficial, and I don't think it really matters. My guess is that we'd get more pushback about extra-files than about the old-name, so that's what this PR does.