Voting starts in March for the Drupal Association Board election.
Several configuration elements have tests for schema compliance but not all. Using capabilities in latest 8.x and the config_inspector module, people can review compliance of the configuration at any point in time on their site with the schema. While there may be (and likely are) holes in the schema for a well developed site, even a default installation of Drupal 8 has schema holes. When installing the standard profile only, there are issues fixed inand additionally optional elements used in views that cause problems.
- display.default.display_options.fields.translation_link.text and display.default.display_options.filters.langcode.value missing schema.
- display.default.display_options.fields.translation_link.text missing schema.
Once providing test for the fixes, another issue with admin_label for blocks ending up in configuration was identified.
In discussion of the views ones with @alexpott and as per him, discussion in Austin resulted in that optional dependencies like that in config entities will not be possible. The only way to get those translation links would be that content translation would need to provide an alternate view on its own for the node and user admin pages. However the feature may not be significant enough to warrant a copy of the view and confusion for the user to select. So we opted not to provide that here and loose this feature instead. Users can add this to the view easily.
For the block admin_label problem, an 'item' type field was identified in BlockBase. The item has no value (only markup), so ends up as an empty string in the data, which makes it appear in the saved configuration. Removing the element from the form data in validation lets us keep the item's visual/structural form without affecting the configuration.
User interface changes
The node admin and user admin views will not have a built-in translation operation in the operation links, even if content translation is enabled. Admins can add this back as part of possible other customizations to these views on the site.
Language views plugins are all moved to views. No API changes other than the placement of the plugins changes, so anything depending on these plugins (unlikely) would need to change their use statements.
|#17||interdiff.txt||748 bytes||Gábor Hojtsy|
|#17||2301045-complete-language-views-fixes-and-tests-17.patch||19.36 KB||Gábor Hojtsy|
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 74,492 pass(es). View
|#15||interdiff.txt||2.03 KB||Gábor Hojtsy|
|#15||2301045-complete-language-views-fixes-and-tests-15.patch||18.63 KB||Gábor Hojtsy|
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 74,466 pass(es), 1 fail(s), and 0 exception(s). View
|#6||2301045-complete-language-views-fixes-and-tests.patch||16.6 KB||Gábor Hojtsy|
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 74,833 pass(es), 3 fail(s), and 0 exception(s). View