Use OfficeIMO 3.1 enums across Word, PowerPoint, and Excel - #162
Use OfficeIMO 3.1 enums across Word, PowerPoint, and Excel#162PrzemyslawKlys wants to merge 11 commits into
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #162 +/- ##
========================================
- Coverage 1.51% 1.51% -0.01%
========================================
Files 564 564
Lines 32479 32489 +10
Branches 5161 5162 +1
========================================
Hits 491 491
- Misses 31940 31950 +10
Partials 48 48 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
PrzemyslawKlys
changed the title
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8b9b5ff2b4
ℹ️ 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".
| <Nullable>enable</Nullable> | ||
| <TreatWarningsAsErrors>true</TreatWarningsAsErrors> | ||
| <OfficeIMOVersion>3.0.1</OfficeIMOVersion> | ||
| <OfficeIMOVersion>3.1.0</OfficeIMOVersion> |
There was a problem hiding this comment.
For clean CI/dev restores that use the default UseOfficeIMOProjectReferences=false, this property feeds every OfficeIMO PackageReference; I checked .github/workflows/test-dotnet.yml and .github/workflows/test-powershell.yml, and they run dotnet restore Sources/PSWriteOffice.sln without overriding that setting. The public NuGet version list for OfficeIMO.Word currently tops out at 3.0.3, not 3.1.0 (see the NuGet versions table), so these jobs will fail during restore until 3.1.0 is published or the workflows use local project references.
Useful? React with 👍 / 👎.
8b9b5ff to
2e09325
Compare
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
PrzemyslawKlys
changed the title
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
PrzemyslawKlys
changed the title
PrzemyslawKlys
changed the title
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c85862041a
ℹ️ 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: 9c102d03f8
ℹ️ 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: 3aecc0c546
ℹ️ 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: 783858a1a8
ℹ️ 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".
2 participants
Summary
Word*alias style and current command parametersWordTableOfContentswhile retainingAdd-OfficeWordTableOfContents-PassThrurow counts on the new OfficeIMO CSV path-PassThruresults-PassThruoutput works with later table-targeting commandsImport-OfficeExcel -AsDataTableUser impact
PowerShell users can pass normal enum names such as
Continuousinstead of Open XML lexical tokens. The same fix applies across section and paragraph breaks, headers and footers, alignment, underline, table layout, protection, text boxes, PowerPoint layouts, and the affected Excel formatting/validation/chart surfaces.For the currently published PSWriteOffice 3.0.0, issue #161 can still use the documented lexical-token workaround. This branch is the clean 3.1 consumer and intentionally requires the coordinated OfficeIMO 3.1 packages.
Release coordination
Merge and publish OfficeIMO 3.1 first, then rerun this PR after the packages are public. Restore/package CI is expected to remain red until that publication; no consumer-side shim, downgrade, or parameter-existence probe is included.