Repository navigation
Ship a designed Python invoice download starter - #36
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 Python web examples currently serve a plain invoice and require a full repository checkout. Give FastAPI, Flask, and Django the designed Northstar invoice, a responsive local download page with keyboard support, separate editable HTML/CSS files, and a builder for a small standalone source ZIP with the actual PDF and preview assets.
The renderer preserves decimal totals, escaped customer text, per-request document state, and private PDF attachment responses. The example remains a fictional, fixed one-page A4 invoice; adapting pagination and application authentication is described in the README.
Validation: all three framework clients and actual local servers passed PDF content, font embedding, header, 404/405, repeated and simultaneous response checks. An independent PDF reader checks the text, including literal markup and placeholder-like customer names. Nine Chrome checks covered all three apps at 1440, 390, and 320 pixels, keyboard activation, downloaded bytes, and staying on the page. The PDF and desktop/mobile previews were visually inspected. Font/license hashes match their pinned sources. CI builds and installs the wheel before its existing Windows/Linux example checks.
Core engine, package dependencies, generated agent contracts, and release versions are unchanged. The standalone download and updated public guide will be published through the documentation repository after this source passes CI.