Last modified: 2007-07-18 01:26:40 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 T12622, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 10622 - boolean converter
boolean converter
Status: RESOLVED WONTFIX
Product: MediaWiki extensions
Classification: Unclassified
ParserFunctions (Other open bugs)
unspecified
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: need-parsertest, patch, patch-need-review
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-07-18 00:31 UTC by Carl Fürstenberg
Modified: 2007-07-18 01:26 UTC (History)
2 users (show)

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


Attachments
the patch (tm) (2.68 KB, patch)
2007-07-18 00:31 UTC, Carl Fürstenberg
Details

Description Carl Fürstenberg 2007-07-18 00:31:14 UTC
Created attachment 3924 [details]
the patch (tm)

Sometimes you want to be able to decide if a parameter is "true" or "false". To make it easier, I propose a boolean function, as specified in accompanied patch. Perhaps some more words could be added, and language specific translations to be implemented (though I don't know where I should put it). I took the decision to say that negative numbers are false.
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-07-18 01:18:59 UTC
Too specialized and language-specific to be worth writing into the extension itself.  Users can make a template.  Recommend WONTFIX.
Comment 2 Rob Church 2007-07-18 01:23:30 UTC
Endorse WONTFIX.
Comment 3 Daniel Cannon (AmiDaniel) 2007-07-18 01:26:40 UTC
Thirded. Too specialized a purpose for a parser function. I agree with Simetrical -- this is better suited as a template on an individual project, not something in the extension itself that will need to be supported. Parser functions should really be reserved for cases that *can't* be handled by templates.

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


Navigation
Links