Update the architecture doc for the ordered-view render-path decoupling - #677
Merged
Joseph Schick (jschick04) merged 1 commit intoAug 12, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates docs/ARCHITECTURE.md to match the post-#672 “ordered-view render-path decoupling” architecture, clarifying the current Runtime/UI responsibilities and the new render/presentation flow.
Changes:
- Documented Runtime’s expanded role (ordered-view render engine + read-sources/change-notifiers) and clarified it depends on Fluxor core rather than
Fluxor.Blazor.Web. - Updated UI description to reflect rendering via
OrderedViewPresentationthroughIOrderedViewSourceinstead of direct FluxorIState<>selector bindings. - Refreshed folder-slice examples and the Event Log performance description to match the shipped columnar store + incrementally-ordered view engine.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Joseph Schick (jschick04)
deleted the
jschick/architecture-doc-render-decoupling
branch
August 12, 2026 16:04
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.
Documentation-only follow-up to the merged ordered-view render-path decoupling (#672). That PR updated
docs/Performance.mdbut notdocs/ARCHITECTURE.md, which still described the pre-migration render path. This reconciles the architecture doc with what shipped:Fluxor.Blazor.Web) so a non-Blazor front end can consume it. The UI renders through the agnosticOrderedViewPresentation(viaIOrderedViewSource) rather than binding FluxorIState<>selectors; Fluxor is retained as the state-management substrate.FilterProgress/slice; movedModal/from the Runtime-mirrored examples to the UI presentation-only list (it now lives only in UI).Performance.md.No code changes.