From: Yury K. <kat...@gm...> - 2014-03-07 07:45:40
|
> Can you elaborate on those weird quantumdynamic anomalies you experience with #set? It's weird but it's the same set of problems Dmitriy is describing about the standard syntax. Sometimes it's UNIQ-QINU errors and sometimes all the properties just don't appear after a certain edit. ----- Yury Katkov, WikiVote On Mon, Feb 24, 2014 at 12:49 PM, Dmitriy Sintsov <sd...@ma...> wrote: > On 24.02.2014 11:23, Yury Katkov wrote: >> >> > 1. Do not use outdated inflexible [[Property::Value]] syntax, use >> > {{#set:property=value}} syntax. >> >> I'd recommend the complete opposite, I don't see how Property::Value >> syntax is outdated or inflexible. In our company we use only this syntax >> since {{#set}} syntax sometimes provokes weird schrodinger's bugs. >> > The parser stage when parser functions are evaluated is properly nested and > purged, while the stage when usual (non-parser functions) wikitext is > evaluated was more prone to various strange bugs (eg. I had UNIQ wrapper > related bugs in my own extensions). > Maybe that's fixed in recent MW's, but I still prefer parser functions for > that reason. If one wants to display the value, he could wrap {{#set}} in > additional template which would output the value. > Dmitriy |