Skip to content

docs: explain inherited ViewModel interaction bindings - #1006

Merged
glennawatson merged 1 commit into
mainfrom
CP_docs-follow-view-model
Oct 13, 2026
Merged

glennawatson merged 1 commit into
mainfrom
CP_docs-follow-view-model

Conversation

@ChrisPulman

Copy link
Copy Markdown
Member

Summary

Explain how interaction bindings follow a typed ViewModel through late assignment, replacement, clearing, and disposal, including a property inherited from a referenced view base. Quote the activation-time issue-board example.

Why

Document the behavior resolved by source generator PR #180, addressing reactiveui/ReactiveUI.Binding.SourceGenerators#170.

Breaking changes

None.

How this was verified

Built the complete website in strict mode and checked that the quoted method and output match the executable documentation example.

Notes for the reviewer

Merge with or after source generator PR #180. The typed property must use a supported notification mechanism for replacement tracking.

Checklist

  • I have read the contribution guidance.
  • The title follows Conventional Commits.
  • Documentation reflects the executable example.
  • Changes target main.

- Explain late assignment, replacement, clearing, and disposal.
- Quote the activation-time issue-board example.
- Document referenced base properties and their notification requirement.
@glennawatson
glennawatson merged commit 43d1be0 into main Oct 13, 2026
4 checks passed
@glennawatson
glennawatson deleted the CP_docs-follow-view-model branch October 13, 2026 03:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants