Open Foxtrek64 opened 10 months ago
I like this proposal! We can keep AggregateError for backwards compatibility, but a more flexible collection-oriented result grouping would be quite nice. I often find myself wanting something better than AggregateError, and this proposal definitely looks like the right direction.
The current AggregateError type is designed to replicate the AggregateException type, but this results in limited utility and is likely one of the least-used error types in the library.
I would like to replace this type with something with more utility, so I'd like to pose the following questions:
Result<T>
types? Do we provide a genericResultCollection<TEntity>
where all contained results must beResult<TEntity>
? Do we keep it non-generic and provide aGetResultOfT<T>()
helper?Here are my thoughts:
ResultCollection
.IResult.IsSuccess