Skip to content

🔧 Drop dead library parameter from Splitter.split() - #610

Merged
MiWeiss merged 2 commits into
mainfrom
chore/drop-splitter-split-library-param
Sep 2, 2026
Merged

🔧 Drop dead library parameter from Splitter.split()#610
MiWeiss merged 2 commits into
mainfrom
chore/drop-splitter-split-library-param

Conversation

@MiWeiss

@MiWeiss MiWeiss commented Sep 2, 2026

Copy link
Copy Markdown
Collaborator

Since #603, parse_string builds a fresh Library and merges the result instead of passing the caller's library into the splitter. That left Splitter.split(library=...) with no caller: nothing in bibtexparser/, tests/, docs/, the README or the notebooks passes it.

Removed the parameter, so split() always returns a new Library (the dead logger.info("Adding blocks to existing library.") branch goes with it). Breaking change to a public signature, which seems right to take now while 2.0.0 is unreleased (2.0.0b9, #609). Splitter and split() stay public and unrenamed; no test called split(library=...), so no test changes.

Merges cleanly with both #598 and #602 — I trial-merged each; #598 touches the adjacent mark regex but does not conflict.

2589 passed, 12 skipped.

🤖 Generated with Claude Code

Since #603, `parse_string` builds a fresh `Library` and merges the
result instead of handing the caller's library to the splitter, so
nothing in the package (or the tests, docs or README) passes
`library=` to `Splitter.split()` any more.

Removing it rather than keeping an unused public parameter, while
2.0.0 is still unreleased (2.0.0b9). `split()` now always returns a
new `Library`; the `Splitter` class and `split()` itself stay public.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@MiWeiss

MiWeiss commented Sep 2, 2026

Copy link
Copy Markdown
Collaborator Author

lgtm

@MiWeiss
MiWeiss force-pushed the chore/drop-splitter-split-library-param branch from febbe96 to ed1bb24 Compare September 2, 2026 20:38
@MiWeiss
MiWeiss merged commit 88ac66a into main Sep 2, 2026
16 checks passed
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.

1 participant