Page MenuHomePhabricator

GRAMMAR functionality should be accessible via hook
Closed, DeclinedPublic

Description

With revision 39077, much of the implementations of the GRAMMAR functionality have been moved from MediaWiki proper to a more appropriate extension. While that is undoubtedly a good thing, there will be a problem with multiple such extensions, or in cases of laguages implementing more general GRAMMAR routines later, e.g. rule based ones.

In order for those to coexist, both a hook-type access to the various GRAMMAR routines would be advisable, and ways allowing them to priorize themselves before being called.

I have not inspected the R39077 changes in depth. Maybe I missed that there is such a mechanism already. In that case, I apologize for bothering you.


Version: unspecified
Severity: enhancement

Details

Reference
bz17242

Event Timeline

bzimport raised the priority of this task from to Lowest.Nov 21 2014, 10:25 PM
bzimport set Reference to bz17242.
bzimport added a subscriber: Unknown Object (MLST).

Grammar functionality has not gone anywhere, it is just the list of names of Wikimedia projects that have been moved to the extension.

Do you have code which would need a hook in there? By the way, the hook system does not allow prioritisation.

I'm with Niklas on this one. GRAMMAR is in core, it just split off some WMF-specific cases to WikimediaMessages, rather than having that in core.

The only use case I could see would be a extension that needs to change the grammar forms defined in WikimediaMessages, which would mean the extension would be Wikimedia-only anyway. Other than that, can't see any correlation.

WONTFIX based on comment 1 and comment 2. There is no proper use case.

I assume to have two in mind, yet many things both about them, and GRAMMAR code, appear vague to me. Too vague, to further discuss it issue now. I may come back later, unless having succeeded implementing them. ;)