- Add the long route for GETing a property specific statement
- Create the GetPropertyStatementRouteHandler class with the usual middlewares and error handling,
- Make sure to handle the new STATEMENT_SUBJECT_NOT_FOUND and INVALID_STATEMENT_SUBJECT_ID use case errors inside the new route handler.
- Find a smart way to make e2e tests on statements work (short/long routes on item/property statements),
Description
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Ifrahkhanyaree_WMDE | T338383 🐐️ Provide data of a statement on a property | |||
| Resolved | • Muhammad_Yasser_Jazirahly_WMDE | T339140 🐐 Implement the "GET Property Statement" long route |
Event Timeline
Change 932423 had a related patch set uploaded (by Muhammad Jaziraly; author: Muhammad Jaziraly):
[mediawiki/extensions/Wikibase@master] REST: Create GetPropertyStatementRouteHandler
Change 937460 had a related patch set uploaded (by Muhammad Jaziraly; author: Muhammad Jaziraly):
[mediawiki/extensions/Wikibase@master] REST: GetPropertyStatementRouteHandler related e2e tests
Change 938282 had a related patch set uploaded (by Muhammad Jaziraly; author: Muhammad Jaziraly):
[mediawiki/extensions/Wikibase@master] REST: Seperate GetStatement e2e tests
Change 932423 merged by jenkins-bot:
[mediawiki/extensions/Wikibase@master] REST: Create GetPropertyStatementRouteHandler
Change 937460 merged by jenkins-bot:
[mediawiki/extensions/Wikibase@master] REST: GetPropertyStatementRouteHandler related e2e tests
Change 938282 merged by jenkins-bot:
[mediawiki/extensions/Wikibase@master] REST: Separate GetStatement e2e tests