Last modified: 2014-07-16 18:00:53 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 T52855, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 50855 - VisualEditor: Transclusions editor should have a special mode for Parser Function and Magic Word calls
VisualEditor: Transclusions editor should have a special mode for Parser Func...
Status: ASSIGNED
Product: VisualEditor
Classification: Unclassified
Editing Tools (Other open bugs)
unspecified
All All
: High enhancement
: ---
Assigned To: Editing team bugs – take if you're interested!
:
Depends on: 49996 62740
Blocks: 46521
  Show dependency treegraph
 
Reported: 2013-07-06 09:49 UTC by Derk-Jan Hartman
Modified: 2014-07-16 18:00 UTC (History)
8 users (show)

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


Attachments

Description Derk-Jan Hartman 2013-07-06 09:49:33 UTC
Parser function syntax is generally {{#function_name : expr1 | expr2 | expr3 | ...}}

Currently VE sees this as a template with name "#function_name : expr1" and arguments "1 = expr2", "2 = expr3", etc. This makes it impossible to edit expr1 in VE.

Same for parserfunctions like urlencode: If the template editor cannot handle these then it shouldn't present an editor for it.
Comment 1 James Forrester 2013-07-07 01:32:43 UTC
Yes, we need a special form of editing transclusions which aren't templates; I can't recall whether Parsoid gives us sufficient information to recognise these as different except for introspection.
Comment 2 NicoV 2013-07-10 14:16:01 UTC
Many of the parser functions are rarely used in the main namespace (#if, ...), but some of them are really important even in the main namespace. For example {{formatnum:...}} is probably used a lot there.

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


Navigation
Links