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
There may be properties on the ImmutableBase<TImmutable> that are not storing relevant data, but instead represent a local caches or syntactic sugar that should actually be ignored when determining the immutable value object's equality, hash code, or string representation.
We should create a [Calculated] attribute that we have consumers flag these properties with so the ImmutableBase<TImmutable> can ignore them.
Task
Add a [Caculated] attribute that ImmutableBase<TImmutable> will look for on all of its child properties and, when found, ignore that property for the purposes of setting it, determining equality, hash code, or string representation. It could, however, be potentially fetched via the GetPropertyValueImpl method.
The text was updated successfully, but these errors were encountered:
Not sure on the name here. I've seen an example of a cache, which [Calculated] doesn't quite fit with. However, the cache probably didn't belong on the immutable value object to begin with, but instead on the service that the cached object came from, so it may be irrelevant.
Background
There may be properties on the
ImmutableBase<TImmutable>
that are not storing relevant data, but instead represent a local caches or syntactic sugar that should actually be ignored when determining the immutable value object's equality, hash code, or string representation.We should create a
[Calculated]
attribute that we have consumers flag these properties with so theImmutableBase<TImmutable>
can ignore them.Task
Add a
[Caculated]
attribute thatImmutableBase<TImmutable>
will look for on all of its child properties and, when found, ignore that property for the purposes of setting it, determining equality, hash code, or string representation. It could, however, be potentially fetched via theGetPropertyValueImpl
method.The text was updated successfully, but these errors were encountered: