Repository navigation
docs: restyle the README like the other SILARHI packages - #361
Merged
Merged
Conversation
CoverageNo Clover report was produced (the PHPUnit jobs failed or were skipped). |
Replace the markdown badges with the centered SILARHI badge row, add a table of contents, features, requirements, testing & quality, contributing, license and footer sections. Keep all existing usage, advanced and troubleshooting examples. Fix the strict/non-strict mode comments (non-strict only tolerates blank operation references) and the format validator example, which trimmed trailing spaces and rejected valid CFONB 120 files.
guillaume-sainthillier
force-pushed
the
docs/readme-style
branch
from
October 1, 2026 08:35
c6b4ee7 to
bbf9ecf
Compare
guillaume-sainthillier
enabled auto-merge (rebase)
October 1, 2026 08:35
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
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.
Aligns the README with picasso-bundle's style: a centered
for-the-badgerow with light and dark variants (stable, downloads, license, PHP, CI, coverage), a centered title and tagline, Features, Requirements, Testing & Quality, Contributing, License, and the SILARHI footer. Existing content is kept, and only verifiable, useful content is added. Every API claim and example was checked againstsrc/and the tests.6.x), title and tagline, table of contents, Features (zero dependencies, supported 120 and 240 record codes, signed amounts, typed getters, LF/CRLF, strict by default), Requirements, Testing & Quality, Contributing, License, footer.src/and the fixtures:Line04Parser); every other error still throws. The old comment said it "continues parsing despite errors".falsefor every valid fixture:trim()stripped the trailing spaces of the last 120-character line. It now normalizes CRLF, trims only newlines, and compares toCfonb120Reader::LINE_LENGTH.