Repository navigation
docs: align ordinary aggregate value rules in v3 - #87
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Document numeric filtering for ordinary sum/sum-distinct and the shared window order for min/max from v3.0.0, preserving v2 type restrictions. Explain nil groups, no matching rows, distinct numeric identity, signed zero, and retained window positions. Architecture text records the existing count-only ordered-group boundary. The merged avg documentation from #86 is preserved.
Refs project-minigraf/minigraf#789. Companion core PR: project-minigraf/minigraf#792.
Validation: the site builder produced all 13 versions and 368 pages with link validation, using a temporary core snapshot with the updated changelog and error reference. Rendered v2.0.11 retains the old restrictions; v3.0.0 shows the new rules and avg content. Claude reviewed the documentation. Comparison/use-case pages and site.toml were audited; no feature matrix, deployment target, or release entry changes are needed.