Repository navigation
feat(web): add framework-independent presentation library core - #787
Closed
behinddwalls wants to merge 1 commit into
Closed
behinddwalls wants to merge 1 commit into
behinddwalls wants to merge 1 commit into
Conversation
## Summary ### Why? Presentation consumers need reusable models, gateway mapping, status/error handling, and refresh behavior without depending on Next.js. ### What? Add the root, server, and testing exports; serializable models; safe timestamp and gateway error mapping; opaque route helpers; single-flight refresh controls; and deterministic fakes. Include library unit/type tests and isolated package-consumer checks. Page-specific widgets are added by later changes. ## Test Plan Passed the six API/library/consumer targets in //web:check. Passed repository formatting, lint, module tidy, and Gazelle checks.
This was referenced Oct 6, 2026
behinddwalls
added this pull request to stack #794
October 6, 2026 21:02
behinddwalls
removed this pull request from stack #794
October 6, 2026 22:08
Collaborator
Author
|
Superseded by a restructured web stack (shared platform package, mountable SubmitQueue module, framework-neutral host pipeline, and Next adapter), which will be published as a new stack. Closing this draft; the branch is kept. |
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.
Summary
Why?
SubmitQueue presentation must be reusable by deployer-owned applications rather than coupled to Next.js or a particular gateway transport.
What?
Introduce the client-safe root, server-only, and testing package exports; serializable models; gateway-to-presentation loaders; safe timestamps and error classification; opaque queue/request path helpers; reusable React views; single-flight automatic/manual refresh; and deterministic gateway fakes. Keep Next.js, authentication, routes, and transport construction outside the library.
Test Plan
Repository-native validation passed:
make test(141 targets),make lint,make check-tidy, andmake check-gazelle. The web generation, lint, typecheck, unit/component, and package-consumer checks passed on the complete stack.Stack