Page MenuHomePhabricator

Fix-up or remove ConvertParser from ParserFunctions
Closed, ResolvedPublic

Description

If someone is going to work further on the ConvertParser stuff (Happy-melon?) it should be left, but if not, as it's potentially rather inaccurate...

If it's not going to be worked on, it should probably be removed (hey, it's in version control) so people don't try and use it to find it not very good.

<TimStarling> Reedy: it is tested, I tested it and found that it was broken
[02:07:54] <TimStarling> it can do many things, but last time I tested it, its precision calculations were wrong, it claimed that 1km = 1mi or something
[02:08:41] <TimStarling> i.e. somehow managing to get less than one significant figure of precision

I'll give it a couple of weeks for a response (maybe) and then will propose a patchset to remove it for now...


Version: unspecified
Severity: normal

Details

Reference
bz40039

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 1:07 AM
bzimport added a project: ParserFunctions.
bzimport set Reference to bz40039.
bzimport added a subscriber: Unknown Object (MLST).

happy.melon.wiki wrote:

This was only ever a path-of-least-resistance attempt to provide a sanely-performing substitute for the virtually-sentient behemoth that is [[Template:Convert]] on enwiki; it never really belonged in ParserFunctions, it was just that at the time we were still in the getting-new-extensions-installed-was-virtually-impossible era.

Now that the ball is *finally* properly rolling on Lua, an extension like this is never going to be as agile (and hence as template-coder-friendly) as a well-written on-wiki Lua script, so I don't have a problem with it being removed; I don't have time to work on it right now anyway, maybe next year (although there are plenty of other things higher up my now-rather-dusty MediaWiki priority list).