[Feature]: Make Avg, StdDev, Maximum and Minimum refresh-aware, consistent with Sum
维护者通常 1 天内回复
评估
调研方向
Read the implementation of Sum and the changes in linked pull request #1219, then trace Avg, StdDev, Maximum, Minimum, Count, IsEmpty and IsNotEmpty through the ForAggregation pipeline. Compare their refresh behavior and decide which operators need stateful projections, immutable variants, or documentation; done means the aggregates behave consistently with the agreed 10.0 model and the release notes describe the behavior and memory impact.
由索引模型根据 Issue 内容生成。
描述
Describe the functionality desired 🐞
The changeset aggregates ignore Refresh. They go through the internal ForAggregation() pipeline, which drops refresh changes, so when an item is mutated in place and refreshed, the aggregate keeps the stale value.
#1167 makes Sum refresh-aware (and adds SumImmutable for the stateless behaviour). Once it merges, Sum will be the only aggregate that honours Refresh, which is inconsistent with Filter, Sort and Group, and with each other: Sum and Avg over the same pipeline would disagree after a refresh.
The remaining aggregates should follow the same model for 10.0.
The steps the functionality will provide
Avg(AvgEx): re-evaluate the selector onRefresh, using stored per-item projections likeSum.StdDev(StdDevEx): same.Maximum/Minimum(MaxEx): same; a refresh can move the extreme value, so the current max/min must be recomputed when the refreshed item held it.Count/IsEmpty/IsNotEmpty(CountEx): no selector, soRefreshcannot change the result. Confirm and document; no behaviour change expected.- Decide per operator whether to add an
*Immutablestateless variant, matchingSumImmutable. - Share one internal stateful helper rather than duplicating the cache and list bookkeeping per operator.
Considerations
Follow-up to #1167. This is a behavioural change (refresh now alters emitted values, and per-subscription memory becomes O(n)), so it should land in 10.0 alongside the Sum change and be called out in the release notes.
- 主要语言
- C#
- 星标
- 1.9k
- 派生
- 194
- 平均合并
- 12 分钟
- 30 天内合并 PR
- 1
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
reactivemarbles/DynamicData 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
reactivemarbles/DynamicData#1229 ·
维护者通常 1 天内回复
-
infrastructure
难度 2/5 1-3 小时 新手友好度 64/100
reactivemarbles/DynamicData#1089 · 1 条评论 ·
维护者通常 1 天内回复
-
[Bug]: ChangeAwareList merges an insert one slot before a pending AddRange, corrupting list order downstream可能已有人在做 @dwcullop 于 9 天前认领。 未关闭bug
难度 3/5 半天 新手友好度 63/100
reactivemarbles/DynamicData#1225 ·
维护者通常 1 天内回复
-
bug
难度 5/5 一周以上 新手友好度 35/100
reactivemarbles/DynamicData#1196 ·
维护者通常 1 天内回复
-
[Bug]: RemoveKey loses entry identity for equal values and produces invalid list indexes可能已有人在做 @dwcullop 于 51 天前认领。 未关闭bug
难度 4/5 3-5 天 新手友好度 35/100
reactivemarbles/DynamicData#1182 · 1 条评论 ·
维护者通常 1 天内回复
查看 reactivemarbles/DynamicData 的全部 Issue
相似的 Issue
-
Feature needs response
难度 2/5 1-3 小时 新手友好度 70/100
Adyen/adyen-dotnet-api-library#1907 ·
维护者通常 5 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 68/100
immichFrame/ImmichFrame#735 ·
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
dimitar-radenkov/Pointframe#318 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
DotHarness/dotcraft#546 ·
维护者通常 1 天内回复
-
a-corriger bug
难度 2/5 1-3 小时 新手友好度 78/100
christian-raj/S-Aloha#303 · 1 条评论 ·