Problem/Motivation
The schema is missing the langcode attribute and doesn't pass the schema validation, basically because the type is mapping and there is no langcode attribute.
Note: This is a really easy task for an applicant for an internship at our organization. I'd appreciate it if you wouldn't work on this unless you are the person whom I sent this issue. If it isn't solved by the end of the week, I will provide a patch myself.
Proposed resolution
Switch the google_analytics.settings type from mapping to config_object.
Remaining tasks
Change the type, provide patch, review and commit it.
User interface changes
None
API changes
None
Data model changes
None
Comments
Comment #2
pravin ajaaz commented@LKS90: Based on your suggestion.
Comment #3
pravin ajaaz commentedComment #4
LKS90 commentedGuess I'll create another one then...
Comment #5
pravin ajaaz commentedOh sorry I didn't noticed it :(
Comment #6
LKS90 commentedThis should be good to go.
No worries, creating a new issue right now. Just don't solve that one :P.
Comment #7
pravin ajaaz commentedHa ha sure I won't. My apologies for this again :( I am glad to help you, If you need.
Comment #8
hass commentedWhat core change has broken this? What about the langcode you posted first? What does this change - change?
Comment #9
LKS90 commented#2541800: Some config do not inherit from config_object, so locale_system_set_config_langcodes() results in schema errors
when switching from mapping to config_object, you just inherit from this very simple core data_type:
Comment #10
hass commentedDoes this also allow per language variables/config without changing anything further? See #2276343: Re-implement per language settings in D8
Comment #11
LKS90 commentedThis only makes the config variables translatable (For example
Web Property ID-->Web Eigentümer ID). You are asking for separate Web Property IDs for each language locale, right?Edit: Looking at the schema my fist assumption doesn't really make sense... I'll play around with this a bit.
Comment #12
hass commentedYes
Translating Web Property ID makes no sense to me as the interface is translated.
Comment #14
hass commentedAnyone has an idea if this allows the translation of the configuration values so we can close #2276343: Re-implement per language settings in D8?
Comment #21
hass commented