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
also, possibly, if there's function called in pass 2 that allocates variables like {{allocate x 5}} then x wouldn't be available from getvarfrom.
Probably best to tell users not to do the latter, but :_generated_body might make sense (also :_relative_url and prepath prefix in the pass 2). Might make sense to have a restricted list of pass 2 variables, and have getvar behave differently with those (though we should proceed with care to avoid the kind of Franklin fuckups...)
The text was updated successfully, but these errors were encountered:
safest (to avoid adding passes and risking to fall back in the @delay pit of doom) is probably to tell people that they should use a dedicated hfun which does:
gets _generated_ihtml
runs html2(...)
this will do more work than required (2x html2 of some content) but is likely easier than to figure out some form of 3d pass re-trigger.
need to have some form of error handling to stop this from looping though... so maybe the function should have a depth indicator so that if a _generated_ihtml contains something that itself wants to call that function, it just fails (depth 1).
Seems like a valid use case is to be able to retrieve something like {{getbodyfrom ...}} / Utils.hfun_getbodyfromUtils.getbodyfrom(...). The Utils.getbodyfrom` would allow users to do some post-processing e.g. if they only want a chunk of it.
e.g.
:_generated_body
also, possibly, if there's function called in pass 2 that allocates variables like
{{allocate x 5}}
thenx
wouldn't be available fromgetvarfrom
.Probably best to tell users not to do the latter, but
:_generated_body
might make sense (also:_relative_url
and prepath prefix in the pass 2). Might make sense to have a restricted list of pass 2 variables, and havegetvar
behave differently with those (though we should proceed with care to avoid the kind of Franklin fuckups...)The text was updated successfully, but these errors were encountered: