Closed Shane32 closed 1 year ago
Possible helper "solution" we could provide: provide a UserContext base class which exposes no members except through the implemented IDictionary<string, object> interface. Users can inherit from this class, and their strongly-typed class will not show any dictionary members on it.
Yes, we can have a UserContextBase
class like you suggest, implementing IDictionary<string, object>
as a helper class
Yes, we can have a
UserContextBase
class like you suggest, implementingIDictionary<string, object>
as a helper class
See attached. Folder / namespace?
See attached. Folder / namespace?
As-is works for me. Thanks
This PR changes
IUserContext
to inherit fromIDictionary<string, object>
so that it can be stored directly withinIResolveFieldContext.UserContext
.Advantages:
See:
However:
IUserContext
in addition toIDictionary<string, object>
, the only requirement for theAddUserContextBuilder<TUserContext>
method within the server project.IUserContext
implementation to inherit fromDictionary<string, object>
Possible helper "solution" we could provide: provide a
UserContext
base class which exposes no members except through the implementedIDictionary<string, object>
interface. Users can inherit from this class, and their strongly-typed class will not show any dictionary members on it.