Bump MinVer from 5.0.0 to 7.0.0#7
Merged
Merged
Conversation
--- updated-dependencies: - dependency-name: MinVer dependency-version: 7.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Owner
|
@dependabot rebase |
Contributor
Author
|
Looks like this PR is already up-to-date with main! If you'd still like to recreate it from scratch, overwriting any edits, you can request |
jkindrix
added a commit
that referenced
this pull request
May 22, 2026
Adds multi-run formatted-string support to random-access cells. New public value records mirror the CellStyle conventions (immutable, structural equality, nullable-axis "inherit existing" semantics): - RichText — sequence of one or more RichTextRun - RichTextRun — (Text, RichTextStyle) pair - RichTextStyle — font-only subset of CellStyle Per-run style is restricted to font axes (Bold, Italic, Underline, FontName, FontSize, Color). Excel's OOXML <r><rPr> element does not honor per-run fills, borders, alignment, or number format — exposing the full CellStyle on a run would silently drop those axes. Cell-level visual style continues through ICell.Style(CellStyle). Run fonts are pooled through the existing CellStylePool font cache (decision #4) — runs with identical font properties share one IFont across the workbook. GetRichText() returns non-null only when the cell carries explicit formatting runs (NumFormattingRuns > 0). A cell set via SetString returns null even though NPOI stores every string cell as an XSSFRichTextString internally. IStreamingCell.SetRichText is intentionally absent. NPOI's SXSSF SheetDataWriter (NPOI 2.7.x) reconstructs a fresh XSSFRichTextString from cell.StringCellValue at flush time, dropping all in-memory formatting runs. Per decision #7 (streaming type-honesty), the absence of the method mirrors the absence of the capability rather than silently degrading or throwing on call. Surfaced during impl by a streaming round-trip test; documented in implementation-notes.md. Surface (30 entries added to PublicAPI.Unshipped.txt): - NetXlsx.RichText (+ Runs, PlainText, ctors, structural equality) - NetXlsx.RichTextRun (+ Text, Style) - NetXlsx.RichTextStyle (+ Bold, Italic, Underline, FontName, FontSize, Color, Default) - ICell.SetRichText(RichText) - ICell.GetRichText() -> RichText? Tests (14 new in tests/NetXlsx.Tests/RichTextApiTests.cs): - value-type semantics (defaults, equality, validation) - in-memory round-trip (SetRichText → GetRichText) - file round-trip via Workbook.Open - GetRichText returns null for plain strings + non-string cells - MaxCellTextLength enforcement on concatenated plain text - Zero-length runs contribute no formatting - IStreamingCell type-honesty: reflection asserts no SetRichText Public-API snapshot + DisposedWorkbookMatrix updated. Design row I-50 added in docs/design.md §6.8.1 with rationale and the SXSSF streaming caveat. Implementation-notes entry captures the SXSSF serializer limitation, the font-only design choice, and the read-side "rich vs plain" discriminator. First slice of the v1.1 roadmap (rich text → tables → images → protection → validation → autofilter → named styles → custom converters → strict concurrency).
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
1 participant
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.
Updated MinVer from 5.0.0 to 7.0.0.
Release notes
Sourced from MinVer's releases.
No release notes found for this version range.
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)