Instead of duplicating them in ImagePage and EditPage.
Bug: T356505
Change-Id: I208fc6f5128205e7620247a3a7c6679e81247058
Co-Authored-By: Timo Tijhof <krinklemail@gmail.com>
While not formally specified in the Stable interface policy, it is
imho not recommended to deprecate a method in a stable class with a
pointer to a method in an `@unstable` class. This sends a mixed signal
to developers.
Keeping this as wrapper method is harmless either way, but I suggest
removing this so that we do not create send automatic nudges to
contributors to change existing code (yet).
Bug: T346211
Change-Id: Iddf8f286e3ffdfce32a8fc2cc95a4e1d4893e146
The array_merge_recursive merge strategy is not intuitive and not
recommended. It does not appear to be used in any of the extensions
or skins that codesearch is aware of. To prevent confusion and
accidental use of array_merge_recursive when the behavior of
array_replace_recursive is likely desired, the array_merge_recursive
merge strategy is deprecated by this patch.
Bug: T292602
Change-Id: Ia0b861c308e6c7b4d40994af4c535ffdfa2b9ff5
The change 4ccc57ff0b cause the error
Uncaught TypeError: request.abort is not a function
in the JavaScript console.
Change-Id: Id431d21e242d64245bc3722e62962a598002d44f
* Deprecate the wgUseSameSiteLegacyCookies configuration variable and
imply false (the previous default).
* Deprecate WebRequest::getCrossSiteCookie(), which was introduced to
support this feature.
* Ignore the sameSiteLegacy option if it is passed to
WebResponse::setCookie() or mediawiki.cookie.set(). The configuration
variable can't be removed until the after the JS change is deployed.
Bug: T344791
Change-Id: I30392ebc02809bc6b6ee2070d3e468e48d5d1fae
Removes a conflicting annotation causing widgets to be
listed in the generated documentation as a class.
Bug: T356723
Change-Id: Ic8e0dd4f7410b16836c93f9b7a580c66b6132f2b
Currently, it is unstyled divs that don't look very well.
Alternative approach to I85e38a9ff16979f
Change-Id: Ic5cb76dbc4c919e059a6648200feecc037326230
This commit introduces PHPUnit test for the MessageFormatterFactory
class. The test ensure that the getTextFormatter method behaves as
expected in various scenarios, including handling different language
codes and message formats.
Change-Id: If54ea938cc851e4728ef70866466afdd82d56ad6
Excludes these methods from the generated documentation
Search results should not be appearing for module.exports
Bug: T352308
Change-Id: Ide2d2d29f36b49d60305ae95cfa7203f02d99985
Allow deletion of files where img_major_mime has a value not allowed by enum (0, '').
Bug: T355530
Change-Id: Ia731af30c32fd14adaf7571210c7703d6097aa54
This adds significant complexity and provides very little value.
As far as I can tell, we've never linked to those IDs. Other headings
in generated documentation don't have fallback IDs (in ApiHelp).
I'm mostly doing this because I want to deprecate and remove
Linker::makeHeadline(), which is a function with really silly
parameters that grew out of a regexp replacement callback in
Parser.php, and which – except for these usages I'm removing
– is only used there.
Change-Id: If793f5023fca744f109f5a1f0f0ad3857375db8c
Why:
* The wgEnablePartialActionBlocks config is marked as unstable,
but also as to be removed before 1.38.
* This is no longer the case as this config is present in 1.42 and
as such this should be removed and instead still indicate this
is unstable without listing a release version for this config.
What:
* Reword the @unstable tag for the wgEnablePartialActionBlocks
to no longer reference a specific release version.
Bug: T280531
Change-Id: I317cd07c42aa59c6a45bf7403fdc79a363880bb5
Make sure all JSDoc descriptions end with a period in
order to populate the summary field in the theme.
Bug: T352308
Change-Id: I787b9c8a59b5e981b78a24f2b380c190eec6a21d
