Hello Yaron
Ya know I was only trying to give some feedback about the extension.
I identified a user-level issue, suggested a solution
... eliminate the (redundant and non-conforming) parameter-name "_table="
that's my 2 cents.. cheers! /john
On 3/31/2015 3:06 PM, Yaron Koren wrote:
Hi,
I don't
Hi,
I don't know what you mean by the vertical bar thing. Again, most MediaWiki
parser functions take either the form:
{{#function_name:a|b|c}}
...or:
{{#function_name:a=b|c=d|e=f}}
#cargo_declare takes the latter form; and the parameters can actually go in
any order.
-Yaron
On Tue, Mar 31,
Hi Yaron,
To the user, 'field_x' looks and acts like a named parameter.
And to the user, _table is even more so a named parameter, as it is
predefined by the extension.
But to the user, this _table parameter appears to be missing a vertical-bar.
And of course a vertical-bar *can* precede that na
Actually, #cargo_declare follows the standard syntax for MediaWiki parser
functions - usually, either all the parameters are named, or none of them
are. #ask is an exception, and #subobject is the very rare exception where
the first parameter is often blank (i.e., your last example).
-Yaron
On Tu
The first parameter in the following syntax seems error-prone.
{{#cargo_declare:
_table=table name
|field 1=field description 1
|field 2=field description 2
...etc.
}}
Normally mediawiki parser functions are either
{#cargo_declare: table name
|field 1=field description 1
|field 2=field descripti
