| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I4b171bedf3a9ef1df7bd11f86c5d7404bd695929
|
|
|
|
|
|
|
|
|
|
| |
Added in 2022 with I7d97c9e2d4 (c6a0d433ec) for Ie430acd075
(e82f11c246) which was (after a revert and re-apply) eventually
removed after the warmup completed (I852060c8a4, 3df4952385).
Bug: T322672
Bug: T387478
Change-Id: I1921b4f985fb27b2227aef4a0eba6751c1c0b8d5
|
|
|
|
| |
Change-Id: I030398e0ef3a20be9a0d500b051e2a3d88ecc01f
|
|\ |
|
| |
| |
| |
| | |
Change-Id: Ic9c1e2051775733672fe8a5378fd3b7ed0a3f652
|
| |
| |
| |
| | |
Change-Id: I94adc67717ac66fc655866f4b8d93bcb758eaace
|
|/
|
|
| |
Change-Id: I2f499c75ce82bd4bb8697b6a950017f0309b2427
|
|
|
|
|
|
|
|
|
|
| |
Almost everywhere else in MediaWiki core and extensions
(at least those used by Wikimedia), it's written
without a space.
Follow up from I4c40a9566642fb2fbcf2006e4b7e33501b7b2575
Change-Id: I952f9552a5300eb883df1b2fc8d9276c42a2c3a6
|
|
|
|
| |
Change-Id: I617c9421a2991a74f1d7aa3cbe05962e36c99de2
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A previous change to add localization strings for the REST extra
routes module was inconsistent between the en/qqq json files and
the message name in php, causing the strings to display incorrectly
in the REST Sandbox. Fix so the messages display correctly.
Bug: T385855
Change-Id: I6c8d825a98ee36218cd23e3945c42010c9bd5ef3
|
|/
|
|
| |
Change-Id: Icbb7ac5c4484bb26e7b69f4118b39d40bef0eb68
|
|
|
|
| |
Change-Id: Ie5ca65e941487bdd0b16a0e1f840a1b642a0d942
|
|
|
|
|
| |
Bug: T353458
Change-Id: I3cf44dfe5425f2efb8409c83571c427447b053af
|
|
|
|
|
|
|
|
|
| |
In MediaWiki/Exception, to follow PSR-4 per plural vs. singular (this can be
changed later if people really care). Also, move the couple of exceptions in
here that were already namespaced in the MW-top-level into the new space.
Bug: T353458
Change-Id: I12ed850ae99effb699a6d7ada173f54e72f0570e
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
In bringing over documentation strings from the API Portal, this one was
garbled. Fix to be sensible.
Change-Id: I74ebd499e91b10487e0ba3e17b8df6efe2116858
|
|/
|
|
| |
Change-Id: I30b0563c4188b53929e6a4109031a827916370f1
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
OpenAPI specs include an "info" section that includes strings such
as "title" and "description" that are intended to be human-readable.
Make all such strings translatable.
Bug: T385855
Change-Id: I15285be6d196c0e7fd7e922f23058d7c09b6b31a
|
| |
| |
| |
| | |
Change-Id: I2fc3a798062df604a9cd283fe2e36921bf03d809
|
|\ \ |
|
| |/
| |
| |
| |
| | |
Bug: T384942
Change-Id: I12c564245113226403298c472f93404dc6b28c2c
|
|\ \ |
|
| |/
| |
| |
| |
| | |
Bug: T382458
Change-Id: Iedd4526a516e8c8e45576a15f3a747a429a2f317
|
|/
|
|
|
|
|
| |
Extending the work began in T3847447, in a continued effort to auto-generate translatable messages in OpenAPI specs, refactor schemas for content.v1 endpoints to accept translatable strings.
Bug: T384750
Change-Id: I95b51021babbed1800ed53ee0066cbe83b3b7535
|
|
|
|
|
| |
Bug: T353458
Change-Id: I35864ad9bd48701703c51367d62f8ebde963c52d
|
|
|
|
| |
Change-Id: Ie7ded5433546e7076e63883b52ea3d405801c510
|
|
|
|
| |
Change-Id: Id4dce6a1b6c111698a71e5531db33d1f47568e0c
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Why:
- Revision meta-data output was failingfor revisions with suppressed
user or comment
What:
- Handle suppressed user and comment gracefully
- add regression test
Bug: T386368
Bug: T387397
Change-Id: Ic6d3fc89d24030f5c3fd422637816de9976fc709
|
|
|
|
| |
Change-Id: Ib9eb4ac69ff3c7361d7873873b02595521a4ddd6
|
|
|
|
| |
Change-Id: Id5b0ff9140433136acad22cf4def5740b583088b
|
|
|
|
| |
Change-Id: I28abfab76b1c7dfa268e7ea2a8c0c50672e87bda
|
|
|
|
| |
Change-Id: Ice1b0bef4d9a0162fcd513410aa31d73deb1ec63
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
As part of the effort to auto generate translatable messages in OpenAPI specs, refactor schemas for content.v1 endpoints to accept translatable strings.
Bug: T384747
Change-Id: I728f0932a770eba56c2ad8e26c74f88fa266a1f9
|
|/
|
|
| |
Change-Id: I357515aef92ea5e98a578a1610113e61785e583a
|
|
|
|
| |
Change-Id: Id3e5ba20513bcad9b6325503116e35381c3cc6f6
|
|
|
|
|
| |
Bug: T376607
Change-Id: I44bbba284e34e8ff53914d9a881598ccb5cb8aa8
|
|
|
|
|
|
|
|
|
|
|
|
| |
is_object is very rarely what we actually need. In many cases we know
exactly what the object can be, and should check for that specific
class or for null.
A database row is an instance of stdClass. Checking that with
is_object also works but is less correct and would allow stuff we
cannot accept in these places.
Change-Id: I1dc663d7325cabc059ef11c4845b0189208e907f
|
|
|
|
| |
Change-Id: Ieda8d483df6c85d6c766414f2e9602f94b9dc85e
|
|
|
|
| |
Change-Id: I5c69db1774f3659b213467e3a238c02a8286f9a8
|
|
|
|
| |
Change-Id: Ie305a422133d22a277a432462aa566dd3a876c9b
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Why: RFC9110 requires 304 "not modified" responses to contain the "date"
and "etag" headers. Failing to include them caused etags to be missing
from responses that were returned from cache after checking the backend
using if-modified-since.
What:
- Make Handler::checkPreconditions() call
applyConditionalResponseHeaders() to add the conditional headers
if the precondition check fails.
Bug: T357603
Change-Id: Ic2e288c971774a561395b3df04bab7256ca62014
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
As part of an effort to increase translation coverage over automated OpenAPI spec generation, use established translation strings for all request body parameters.
Bug: T378375
Change-Id: If678d7177bd09e3bdc5bc0cd1605a43dc825eb5c
|
| | |
| | |
| | |
| | | |
Change-Id: I5495becb444413be27e0f2831adddaf5696834a3
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add $string === false or $string === null where $string can have other
types than a string.
Also document null as possible return value in FileRepo.
Change-Id: Iaa29ba01c3fd6bea506debdc6f929edfe881c808
|