Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
configuration entity system
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
12 Jan 2015 at 17:15 UTC
Updated:
9 Feb 2015 at 11:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
gábor hojtsyProposed patch using "with_overrides" language.
Comment #3
gábor hojtsyComment #5
hass commentedPlacing a boolean in quotes looks wrong to me. We have boolean type for variables in .yml files.
Comment #6
gábor hojtsysystem.routing.yml and other routing files are full of
It is true that some things use TRUE (without quotes) even in system.routing.yml, there is no real consistency. It does not actually matter from the code if its a string or a bool, if its 'TRUE' or TRUE, it evaluates to true either way.
Comment #7
hass commentedI was not aware of this. I only remembered when I defined types in schema files of my modules I started to run into issues when I tried to save a wrong type.
Comment #8
gábor hojtsy@hass: config files saved using config schema will enforce types, routing.yml are developer written and does not enforce types for values programatically.
Comment #9
hass commentedThat is very inconsistent. DX fail.
Comment #10
hass commentedCreated followup #2406397: Change all values in yml files to correct data type
Comment #11
jhodgdonPatch looks good to me.
We will need to have a change record and beta evaluation.
Also, adding link to original issue where this parameter was added. As a note there was no change record there.
Comment #12
olli commented#2137595: 'Create @name' page title uses override-free configuration (eg. not localized) instead of the overridden configuration (eg. localized) landed.
Comment #13
gábor hojtsyAdded change notice at https://www.drupal.org/node/2407035 (draft), added beta evaluation to issue summary. @jhodgdon: what do you think? :)
Comment #14
jhodgdonLooks good, thakns! I think the change notice should mention the previous name of the parameter, so I added a short note. This would allow someone whose contrib module using the old option suddenly broke to search and find this change notice.
Comment #15
gábor hojtsy@jhodgdon: thanks. Looks like all this needs is a review confident to RTBC :)
Comment #16
jhodgdonI have verified that this patch changes all current Core uses of 'use_current_language' to 'with_overrides'. I think the new parameter name is clearer than the old. Tests pass. There's a beta evaluation and a change notice.
Let's do it!
Comment #17
gábor hojtsyAssigning to @alexpott as #2392319: Config objects (but not config entities) should by default be immutable might necessitate changing the terminology here.
Comment #18
alexpottLet's go with
with_config_overrides. I don't think aligning to thegetEditable()terminology from #2392319: Config objects (but not config entities) should by default be immutable is relevant - since entities (including config entities) are mutable.Comment #19
gábor hojtsyRolled with that name. Updated issue summary and change notice.
Comment #20
develcuy commentedComment #21
develcuy commentedRemoved SprintWeekend2015Queue by mistake.
Comment #22
alexpottYep
use_current_languageis a bad name when this relates to config overrides. Committed cc9d0f9 and pushed to 8.0.x. Thanks!Comment #24
gábor hojtsy