Let us summarize the behavior in question.
You have a template A which calls a macro M which in turn calls a
template B.
A defines $foo, B changes its value, and you want the new value to be
visible in A but not in M. Is that right? Even worse, if M changes the
value, you want the new value
I definitely do understand Velocity side and I never been a big fan of
the previous magic behavior but I have to wear the retro compatibility
nazy hat right now :D
I don't have much confidence in me proposing a patch that would not
break more than it fix but yes that's my next step. What I definit
Oh yeah, i understand that from your side totally! Paying of tech debt for
big upgrades takes a long time, and i'm super grateful for your
thoroughness this time around. I'm just saying from the Velocity dev side,
it seems odd to re-add a large, complicated feature (the explicit macro
scopes are mu
On Wed, Jan 15, 2020 at 5:31 PM Nathan Bubna wrote:
>
> I don't have any time for dev work on Velocity these days, so it doesn't
> much matter whether i consider it or not. :) If someone wants to put in the
> work, i won't protest.
> My inclination, ineffectual though it may be, is to
> point out
