feat: pyramid_components for HTML elements - #20593
Open
miketheman wants to merge 2 commits into
Open
miketheman wants to merge 2 commits into
miketheman wants to merge 2 commits into
Conversation
miketheman
added this pull request to stack #20597
September 24, 2026 19:03
miketheman
changed the title
miketheman
added
python
miketheman
marked this pull request as ready for review
September 24, 2026 19:07
This branch has not been deployed
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.
pyramid_componentslets a UI unit be defined as a typed Props contract plus a co-located template, and rendered from Jinja2 with a{% component "name", kw=val %}tag.It ships a
Componentbase class, the props-to-dataclass binding, a module-level registry whoserender()is the single path all rendering goes through, the Jinja2 extension, and a Pyramidincludeme.Review other parts of the stack to see how the package remains isolated and the leverage is in defining our own components and calling them in template code.
These are a few admin-related examples that are useful for proving the concepts, before considering more refactoring in the main code for items like common forms behaviors - that should also be explored in admin first.
Signed-off-by: Mike Fiedler miketheman@gmail.com