https://bugzilla.wikimedia.org/show_bug.cgi?id=23693

           Summary: The syntax of the {{{info}}} field is 'fragile'
           Product: MediaWiki extensions
           Version: any
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: Normal
         Component: SemanticForms
        AssignedTo: [email protected]
        ReportedBy: [email protected]
                CC: [email protected]


I'm using the {{{info}}} form field to specify a page name so that I can use
the #forminput; parser function. However, I find that the syntax of the field
is incredibly 'fragile', which really hampers my 'debugging' process (using
forminput can be confusing, especially if it requires a complex 'query
strying').

For example, this fails to correctly start the page name unique number at 0:
{{{info | page name=Dummy page <unique number; start = 0>}}}

But this works (no spaces between the final equals sign):
{{{info | page name=Dummy page <unique number; start=0>}}}


Similarly, this fails to correctly set the page name at all:
{{{info | page name = Dummy page <unique number; start=0>}}}

But this works (no space between the first equals sign):
{{{info | page name=Dummy page <unique number; start=0>}}}


Finally, this fails to correctly set the page name at all:
{{{info 
 | page name=Dummy page <unique number; start=0>
}}}


All of the above attempts around the correct syntax were tried in a effort to
make the form tags more readable, making the overall form easier to understand
(especially for beginners). I think white space, including newlines, is
generally accepted to improve readability, and should be encouraged.

The failure of these syntax variants is inconsistent with the way templates
(and often parser functions) work in MW.


Similar problems may affect the other form tags, but this has not been
investigated.

-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to