You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current pattern, which requires explicitly settings the Source property in the ctor, is non-obvious. We should be able to call base(source) and get the same effect, but we can't do that because we're calling this(). It feels like there should be a better way to do this so that aggregates can use that base ctor instead of having to set Source directly.
One option would be to add the following to the standard pattern for aggregates:
The current pattern, which requires explicitly settings the
Source
property in the ctor, is non-obvious. We should be able to call base(source) and get the same effect, but we can't do that because we're calling this(). It feels like there should be a better way to do this so that aggregates can use that base ctor instead of having to set Source directly.One option would be to add the following to the standard pattern for aggregates:
I believe we need to keep the parameterless ctor for deserialization, but this would give a slightly cleaner pattern for devs to use.
The text was updated successfully, but these errors were encountered: