Inspired by #1938570: Make views active config save format match the default yml file (order and quotes)

Problem/Motivation

Some active config files (like sites/default/files/config__rzyR0s0KXhc9jjr4I7HQl3nK300t-85ew12vzYGO2A/active/something.else.whatever.yml) are saved with a different format than the default yml files (under core modules config directories like core/modules/something/config/something.else.whatever.yml).

Proposed resolution

check the files by resaving configurations, and diffing them.
open issues for ones that differ, and add to the list of issues in the issue summary.
make a comment here and update the issue summary for ones that are confirmed to match.

Remaining tasks

make a list of ones that need to be checked.

Sub-Issues

Files checked that are ok and do not need issues

  • action.settings.yml
  • aggregator.settings.yml
  • book.settings.yml
  • dblog.settings.yml
  • file.settings.yml
  • field.settings.yml
  • node.settings.yml
  • search.settings.yml
  • filter.format.php_code.yml
  • rest.settings.yml
  • shortcut.settings.yml
  • simpletest.settings.yml
  • statistic.settings.yml
  • text.settings.yml
  • tracker.settings.yml
  • update.settings.yml

Files checked that are not very sure or need further review

  • translation.settings.yml
  • translation_entity.settings.yml

User interface changes

No UI changes.

API changes

No API changes.

Steps to reproduce#

  1. Install as usual
  2. Install the module that needs check and visit the module's config folder for the configuration file name
  3. find the same file in sites/default/files/config_[hash]/active folder.
  4. Compare both files with some diff tool

Coding standards#

  1. Do not use double quotes for strings, use single quotes.
  2. Use single quotes for label values even if they are one word for consistency.
  3. Never use quotes for key definitions and types (in Drupal, key names and types are strings by definition and should not have spaces).
  4. In Drupal, integer values contained YAML config data files are cast to string and therefore are wrapped in single quotes.
  5. Watch your indentation levels. This is not a code style requirement per say, since it is important to use proper indentation in YAML so you get the desired schema structure.

Comments

YesCT’s picture

Category: bug » task

I think the meta can be a task, and the sub issues will be bugs.

YesCT’s picture

Component: views_ui.module » configuration system
heyrocker’s picture

Issue tags: -CMI +Configuration system
vijaycs85’s picture

Issue summary: View changes

Updated issue summary with coding standard and step to check.

vijaycs85’s picture

Issue summary: View changes

Updated issue summary updating # key

vijaycs85’s picture

Issue summary: View changes

Updated issue summary - # update

vijaycs85’s picture

Issue summary: View changes

Updated issue summary.

vijaycs85’s picture

Issue summary: View changes

Updating modules that are ok

vijaycs85’s picture

Issue summary: View changes

Adding additional issues and files

vijaycs85’s picture

Issue summary: View changes

Updated issue summary with HTML fix

vijaycs85’s picture

Issue summary: View changes

Updated issue summary with HTML fix

YesCT’s picture

Trying to figure out where the standards come from
http://drupal.org/node/1905070 is the d.o doc page pointed to from the change record (http://drupal.org/node/1905120) form the issue #1866610: Introduce Kwalify-inspired schema format for configuration

YesCT’s picture

YesCT’s picture

YesCT’s picture

dblog is listed as not needing an issue.. but I think: #1930226: Update integer/boolean values with quotes in configuration files.

YesCT’s picture

Issue summary: View changes

Updating minor ucfirst

YesCT’s picture

Issue tags: -Novice
YesCT’s picture

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

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should 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.

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

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should 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.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should 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.