Modernize PowerShell DSL and parameter contracts - #187
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0158b76352
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5fb6bf04e4
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Summary
OfficeWord,OfficeExcel,OfficePowerPoint,OfficePdf,OfficeMarkdown,OfficeRtf,OfficeVisio, andOfficeOpenDocumentDSL roots while retaining the canonicalNew-Office*commands#AARRGGBBcontract while normalizing shorthand colors consistently across all Excel color parametersBackgroundColor Nonea portable rich-text reset for Word, PDF, and PowerPoint adapters; Excel safely ignores unsupported run backgroundsPowerShell usage
Existing
New-Office*commands and established DSL aliases remain available. PowerShell still converts valid string literals to enum values, while invalid closed-domain values now fail during parameter binding. Open or renderer-extensible domains remain strings and receive completion without being artificially closed.Validation
net8.0andnet472builds