Skip to content

docs(mutator-framework): Add JSDoc for public APIs [skip chg] - #12211

Merged
Timothee Guerin (timotheeguerin) merged 11 commits into
microsoft:mainfrom
timotheeguerin:docs/jsdoc-mutator-engine
Oct 16, 2026
Merged

Timothee Guerin (timotheeguerin) merged 11 commits into
microsoft:mainfrom
timotheeguerin:docs/jsdoc-mutator-engine

Conversation

@timotheeguerin

@timotheeguerin Timothee Guerin (timotheeguerin) commented Oct 15, 2026 •

Copy link
Copy Markdown
Member

Mutation authors need to distinguish registered graph state, replacement results, traversal callbacks, and concrete mutation helpers without inferring their lifecycle from implementation.

Document the public mutation framework together, from engine and graph contracts through model/operation, scalar/enum/union, value, and tuple mutations. Clarify ownership and replacement semantics without changing mutation behavior.

Consolidates 12216, 12219, 12222.

Tracked in #12228.

@pkg-pr-new

pkg-pr-new Bot commented Oct 15, 2026 •

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/@typespec/mutator-framework@12211

commit: ed4e237

@github-actions

Copy link
Copy Markdown
Contributor

All changed packages have been documented.

  • ✅ @typespec/mutator-framework
Show changes

@typespec/mutator-framework - internal ✏️

Clarify mutation strategy identity, caching, and single-node engine contracts.

@timotheeguerin Timothee Guerin (timotheeguerin) changed the title docs(mutator-framework): explain mutation engine contracts docs(mutator-framework): Add JSDoc for mutation engine contracts [skip chg] Oct 15, 2026
@azure-sdk-automation

azure-sdk-automation Bot commented Oct 15, 2026 •

Copy link
Copy Markdown

You can try these changes here

🛝 Playground 🌐 Website 🛝 VSCode Extension

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The changes are documentation-only, with one non-blocking clarification about constructor arguments.

1 open finding
What changed in this PR

Documents mutation-engine contracts for custom strategy authors as part of #12228, without changing APIs or runtime behavior.

Changes:

  • Explains strategy identity, caching, and deferred connections.
  • Documents single-node strategies and unused option inputs.
  • Adds an internal changelog entry.
File Description
packages/​mutator-framework/​src/​mutation/​simple-mutation-engine.ts Documents single-node strategies and options.
packages/​mutator-framework/​src/​mutation/​mutation.ts Explains strategy lifecycle and cache metadata.
packages/​mutator-framework/​src/​mutation/​mutation-engine.ts Documents registries, contexts, caching, and connections.
.chronus/​changes/​docs-jsdoc-mutator-engine-2026-9-15-11-57-44.md Records the documentation update.

🧠 Review effort: Balanced


💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.


/**
* Mutation inputs together with the selected cache identity.
* Describes the combined context; constructors receive these values positionally.
Copilot AI balanced review requested due to automatic review settings October 16, 2026 14:12
@timotheeguerin Timothee Guerin (timotheeguerin) changed the title docs(mutator-framework): Add JSDoc for mutation engine contracts [skip chg] docs(mutator-framework): Add JSDoc for public APIs [skip chg] Oct 16, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The changes are documentation-only, with no API or runtime changes and no unresolved review issues.

1 open finding

🧠 Review effort: Balanced

@timotheeguerin
Timothee Guerin (timotheeguerin) merged commit 673cab7 into microsoft:main Oct 16, 2026
31 of 33 checks passed
@timotheeguerin
Timothee Guerin (timotheeguerin) deleted the docs/jsdoc-mutator-engine branch October 16, 2026 16:19
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.

2 participants