Extract `ic_agent::identity` module into a standalone crate
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 144
- Forks
- 84
- Avg merge
- 20h 4m
- Merged PRs (30d)
- 1
Description
The ic-auth-client crate currently depends on ic-agent. However, it actually only uses the identity module within it. Despite this limited usage, version updates to the entire ic-agent crate require breaking changes and updates to ic-auth-client due to compatibility issues.
If you could publish the identity module as an independent crate, similar to ic_principal, it would reduce the maintenance overhead for ic-auth-client and the burden on its users. Could you please consider this request?
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 inspecting the identity module in ic-agent and its usage in ic-auth-client; compare the standalone ic_principal crate for package structure and publishing conventions. Define the independent crate boundary and compatibility requirements, then verify that ic-auth-client can use it without depending on ic-agent and that the new crate is publishable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100