paritytech / paritytech/host-rust-core
Simplify SSO request and response encoding
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 10
- Forks
- 3
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 148
Description
Use separate SSO request and response enums, with correlation metadata in a shared response envelope. Dispatch directly on requests to eliminate the extra classification types.
Version the wire-format change and update both peers, the spec, and compatibility fixtures together.
Follow-up to #628.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading follow-up issue #628 and tracing the SSO request and response definitions, the protocol spec, and compatibility fixtures. Compare both peers’ wire-format handling, then verify that the versioned format, shared response envelope, and direct request dispatch are consistent across the spec and fixtures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100