Last modified: 2014-03-06 18:21:32 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T55413, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 53413 - TemplateData: Consider support for non-template transclusions (magic words, parser functions)
TemplateData: Consider support for non-template transclusions (magic words, p...
Status: ASSIGNED
Product: MediaWiki extensions
Classification: Unclassified
TemplateData (Other open bugs)
unspecified
All All
: High normal (vote)
: ---
Assigned To: Editing team bugs – take if you're interested!
:
Depends on:
Blocks: 52607 53414
  Show dependency treegraph
 
Reported: 2013-08-27 18:11 UTC by Krinkle
Modified: 2014-03-06 18:21 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Krinkle 2013-08-27 18:11:06 UTC
Right now it is only intended for data about custom wiki-made templates.

To support magic words and parser functions, we'll need to make a few changes to make sure there are no conflicts or wrong assumptions.

A few random points:
* 'titles' parameter in the API module
* The PHP parser prefers native magic word over templates (creating Template:PAGENAME and using {{PAGENAME}}, will not use that template).
* Should there be an implied property 'type':
  - type:template -> {{Foo}}, {{:Foo}}, {{Template:Foo}}, {{Project:Foo}}
  - type:parserfunction -> {{PAGENAME}}, {{urlencode:123}}, {{#special:Watchlist}}

* parser functions don't have numerical parameters, and the first parameter is separated by colon, not by pipe. So we need a way (both in TemplateData and VisualEditor) to insert unnamed parameters without using numbers.

 e.g. {{urlencode:Foo|WIKI}} is correct, but {{urlencode:Foo|1=WIKI}} or {{urlencode:1=Foo|2=WIKI}} or {{urlencode|1=Foo|2=WIKI}} is wrong.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links