Maybe usercontext should not be a top-level thing, because we might need context for other entities (say field label translation based on node language).
Make a generic top-level context and make user context extend that generic entity context.
No UI changes.
Yes?
Follow up for #1763640-207: Introduce config context to make original config and different overrides accessible and #208
@catch:
I'm not really sure about usercontext being a top-level thing, isn't it possible we'd need context for other entities (say field label translation based on node language) - if we do then the user context could extend a generic entity context. However so far it's the only one that's needed so could just be follow-up.
#208
@GaborHojtsy:
- as for user context being top level, earlier proposals (eg. #27 above) had a generic object context which then was further specialised into a user context; I think this can be introduced later once we have some practice.
Comments
Comment #1
yesct commentedpostponed on #1763640: Introduce config context to make original config and different overrides accessible
Comment #2
gábor hojtsy#1763640: Introduce config context to make original config and different overrides accessible committed now. We should also ideally have a specific language object context for when someone wants to access a specific language based override. Although we might not need that per say in core, having contexts that contrib can rely on and attach to is important so there are no different modules implement different contexts. Writing it down here to inform the class structure.
Comment #3
alexpottThe config context system was removed in #2098119: Replace config context system with baked-in locale support and single-event based overrides