Repository navigation
Try PDF components directly from the homepage and React starter - #105
Merged
Merged
Conversation
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.
The homepage now opens a working component-authored invoice. Users can edit rows, credits, payment state and colors, download the resulting PDF, and open the same typed component project in the source editor or ZIP. The React guide explains the document-aware preview hook and the Vite configuration needed for print component and style edits to refresh the PDF.
The ZIP contains the exact source reviewed in fullbleed-engine/fullbleed-node#38, using published fullbleed 0.6.0 and unchanged engine 2.5.24. The launcher selects src/documents/Invoice.tsx. Existing HTML invoice/report designs remain available, and the other online launchers are byte-identical.
Validation: the source passed all 16 CI jobs, including Chrome, Firefox and WebKit, development StrictMode, and actual TSX/stylesheet edits. Locally, the exact downloadable ZIP installed from a fresh cache and built successfully; the actual guide TSX example type-checked; the resulting demo passed 124 browser checks with six component PDF/PNG comparisons against Node. The online form submits all 20 source files from the ZIP. Homepage/guide checks at 1440, 390 and 320 pixels exercised the actual PDF and ZIP downloads. Strict MkDocs and internal paths, anchors and metadata passed for 87 pages. The docs workflow repeats installation, guide compilation and browser validation before deployment.
An anonymous StackBlitz launch also installed and started this exact project. Its default PDF matched the Node baseline, and an edited-customer PDF downloaded with the expected text. The external editor emitted source-file lookup diagnostics while loading; these are retained separately from the successful preview/download evidence.