Hey,
Thanks for expalining.
I did notice the code now resides in a seperate library. Congratulations on
that work. I can see how this provides benefit.
It is also clear that naming it wfSuppressWarnings there does not make a
lot of sense. What is not clear to me is why existing MediaWiki extensi
On Mon, 22 Jun 2015 at 09:00 Legoktm wrote:
> Hi,
>
> On 06/21/2015 01:52 PM, Jeroen De Dauw wrote:
> > Hey all,
> >
> > This thread is much in line with the "wfRunHooks deprecation" one from
> > January. Rather than turning global functions into static functions, this
> > time it's about namespa
Hi,
On 06/21/2015 01:52 PM, Jeroen De Dauw wrote:
> Hey all,
>
> This thread is much in line with the "wfRunHooks deprecation" one from
> January. Rather than turning global functions into static functions, this
> time it's about namespacing global functions.
>
> All extensions calling wfSuppres
Hey all,
This thread is much in line with the "wfRunHooks deprecation" one from
January. Rather than turning global functions into static functions, this
time it's about namespacing global functions.
All extensions calling wfSuppressWarnings now are supposed to change this
to MediaWiki\suppressWa