Follow-up from #1653026: [META] Use properly typed values in module configuration.

Problem/Motivation

All integers, Booleans, and even octal numbers in config object files are converted to strings.

Proposed resolution

#1653026: [META] Use properly typed values in module configuration has fixed core, so no need to convert all data types to string anymore.

Remaining tasks

entity.view_mode.taxonomy_term.full.yml
taxonomy.settings.yml
views.view.test_filter_taxonomy_index_tid.yml
views.view.test_groupwise_term.yml
views.view.test_taxonomy_node_term_data.yml

User interface changes

NO

API changes

NO

Parent: #1653026: [META] Use properly typed values in module configuration

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

alexander_danilenko’s picture

Assigned: Unassigned » alexander_danilenko
Status: Active » Needs review
FileSize
10.55 KB

Huw about items_per_page_options: '5, 10, 20, 40, 60' ?

I think it's needed as string, because arrays should looks like:
items_per_page_options: [5, 10, 20, 40, 60]

The last submitted patch, 2105997-1-taxonomy-yaml-variable-type.patch, failed testing.

vijaycs85’s picture

Issue summary: View changes
Status: Needs work » Needs review
FileSize
9.49 KB

Re-rolling...

vijaycs85’s picture

Status: Needs review » Closed (duplicate)
Related issues: +#2167623: Add test for all default configuration to ensure schema exists and is correct

The patch on this issue has been updated as part of #2167623: Add test for all default configuration to ensure schema exists and is correct. As this issue doesn't have any test to confirm/validate the schema, making this change and closing this issue as duplicate of #2167623: Add test for all default configuration to ensure schema exists and is correct. The contributors of this issue (in commit message) is copied to #2167623: Add test for all default configuration to ensure schema exists and is correct.