Skip to content

Update roadmap with Actix API subtasks #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
leynos merged 2 commits into from
Jun 11, 2025
Merged

Update roadmap with Actix API subtasks #4

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1e57c1d
Detail Actix API subtasks
leynos Jun 11, 2025
992d6bc
Expand API roadmap subtasks
leynos Jun 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions docs/roadmap.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,20 @@ after formatting. Line numbers below refer to that file.
329-333).
- [ ] Build the Actix-inspired API around `WireframeApp` and `WireframeServer`
as described in lines 586-676.
- [ ] Implement `WireframeApp` builder.
Clarify method signatures (`new`, `route`, `service`, `wrap`),
expose a consistent `Result<Self>` error strategy, and allow
registration calls in any order for ergonomic chaining.
- [ ] Implement `WireframeServer`.
Outline how worker threads are spawned via Tokio, with graceful
shutdown using a signal and per-worker `WireframeApp` instances.
- [ ] Standardise supporting trait definitions.
Provide naming conventions and generic bounds for the
`FrameProcessor` trait, state extractors and middleware via
`async_trait` and associated types.
- [ ] Provide a minimal, runnable example.
Include imports and an async `main` so the snippet compiles out of
the box.

## 2. Middleware and Extractors

Expand Down
Loading