This is a sub-issue of #1910624: [META] Introduce and complete configuration schemas in all of core.

Problem/motivation

#1866610: Introduce Kwalify-inspired schema format for configuration introduced the idea of config schema. The changelog leads to (hopefully extensive) documentation on the format at http://drupal.org/node/1905070. While there are little cleanups planned for the format overall, the current format is a result of months of back and forths, so it should be perfectly fine to apply it more widely to core.

Proposed solution

Create a configuration schema for php module.

Schema in place

Schema not yet in place
filter.format.php_code.yml

CommentFileSizeAuthor
#1 19191912-php-schema-1.patch735 bytesvijaycs85
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

vijaycs85’s picture

Status: Active » Needs review
FileSize
735 bytes

Adding schema file...

Status: Needs review » Needs work
Issue tags: -Configuration system, -D8MI, -language-config, -Configuration schema

The last submitted patch, 19191912-php-schema-1.patch, failed testing.

vijaycs85’s picture

Status: Needs work » Needs review
Issue tags: +Configuration system, +D8MI, +language-config, +Configuration schema

#1: 19191912-php-schema-1.patch queued for re-testing.

vijaycs85’s picture

Status: Needs review » Closed (won't fix)

After discussing with @sandipmkhairnar, realized that this configuration is already covered in #1919174: Create configuration schemas for filter module. So closing it with "won't fix".

Gábor Hojtsy’s picture

So #1919174: Create configuration schemas for filter module does not actually have PHP module specific schema, but there are no specific schema elements needed beyond what is already in filter as a general coverage. That is ok I think.