Now that T319054: Upgrade vendor's copy of opis/json-schema to 2.x is resolved, making use of opis/json-schema library for validating json schemas should be possible. It should also allow to tackle T351879: Support i18n in validation errors in a simpler way that currently with justinrainbow, see also T351879#9437753.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Jdforrester-WMF | T293710 Remove opis/json-schema from MW vendor now that it's no longer used, everyone's on justinrainbow/json-schema | |||
| Declined | None | T388380 Migrate Community Configuration PHP library from justinrainbow/json-schema to opis/json-schema |
Event Timeline
Comment Actions
Reviewing this again in light of the update of justinrainbow/json-schema (T412876, T415261), we have decided that the migration to opis/json-schema is not worth it. It seems to us, that what we would potentially stand to gain is not worth the effort required by the migration.
CommunityConfiguration still needs more things done, like T370534 (T410459), T371028, T367516. But any localization issues with error messages have not come up as a priority since its launch.
We're open to revisiting this should new reasons for a switch materialize in the future, including if the Wikimedia movement were to adopt opis/json-schema as only json-schema library for some reason. But for now, none of that has happened or seems likely. Thus declining this task.
(For future reference, the conversation about this in the private #growth-engine-room Slack channel: https://wikimedia.slack.com/archives/GVD7X37RB/p1769022399873089 .)