Change Details

To increase the chances of adoption of Community Configuration i18n support is very desirable. opis/json-schema does not provide the feature (see T332847). >>! In T332847#9230079, @Tgr wrote: > Opis has ValidationError::$keyword, maybe that can be used as a key? It's not obvious at a glance if it has an 1:1 relationship to error messages. > > If not, it might be worth a feature request to ask them to add a unique key for each error type. The goal of this task is to research if using the library as it is now allows to wire MW's localisation system.

To increase the chances of adoption of Community Configuration i18n support is very desirable. opis/json-schema or justinrainbow/json-schema does not provide the feature (see T332847). >>! In T332847#9230079, @Tgr wrote: > Opis has ValidationError::$keyword, maybe that can be used as a key? It's not obvious at a glance if it has an 1:1 relationship to error messages. > > If not, it might be worth a feature request to ask them to add a unique key for each error type. The goal of this task is to research if using the library as it is now allows to wire MW's localisation system.

To increase the chances of adoption of Community Configuration i18n support is very desirable. opis/json-schema or justinrainbow/json-schema does not provide the feature (see T332847). >>! In T332847#9230079, @Tgr wrote: > Opis has ValidationError::$keyword, maybe that can be used as a key? It's not obvious at a glance if it has an 1:1 relationship to error messages. > > If not, it might be worth a feature request to ask them to add a unique key for each error type. The goal of this task is to research if using the library as it is now allows to wire MW's localisation system.