Problem/Motivation
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).
Proposed resolution
Make a generic top-level context and make user context extend that generic entity context.
Remaining tasks
- Get some practice with context, via other issues
- Discuss
User interface changes
No UI changes.
API changes
Yes?
Original report by @catch
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.