Parallel issue to #1696648: [META] Untie content entity validation from form validation, but for config. Placing this in the "configuration entity system" component for now, though possibly we want to cover single config as well?

Currently, core does not implement web services (i.e., a REST plugin) for config. However, contrib may wish to. Contrib will have a difficult time doing that if there's no way to validate config independently of a form submission.

Comments

jhedstrom’s picture

Category: Task » Plan
alexpott’s picture

Version: 8.0.x-dev » 8.1.x-dev

This can't be done during 8.0.0 so postponing to 8.1.x

alexpott’s picture

Status: Active » Postponed
xjm’s picture

@alexpott, @cilefen, and I discussed these issues today during a CMI meeting.

The title of this issue is a little misleading as "config validation" is a different thing from the kind of validation for data done on form submission. I was going to retitle it to "use API validation for configuration entity data" or something like that. Seems like implementation-wise there is overlap with #1928868: Typed config incorrectly implements Typed Data interfaces and the potential blocker #1818574: Support config entities in typed data EntityAdapter?

xjm’s picture

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Wim Leers’s picture

Does this just mean perform config schema validation every time config is saved?

Wim Leers’s picture

Status: Postponed » Active

And I don't think this needs to be postponed anymore? This can be worked on now.

dawehner’s picture

Well, conceptually #1928868: Typed config incorrectly implements Typed Data interfaces would solve the underlying API capabilities. This issue is then more about organizing an effort to add all the various constraints .

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.