alchemyplatform / alchemyplatform/aa-sdk
docs: privy integration guide - apiKey not being passed as expected
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 321
- Forks
- 231
- Avg merge
- 43m
- Merged PRs (30d)
- 3
Description
Is this a request for new documentation or updates to existing documentation
When using Privy integration guide, the apikey is not passed through the client correctly leading to a http transport error. rpcUrl must be passed instead
If existing documentation, a clear summary of what needs to be changed
A clear and concise description of what documentation should be changed, and a link to the resource that needs the update.
If new documentation, a clear summary of what needs to be added
A clear and concise description of what documentation should be added.
Additional context
Add any other context or screenshots about the feature request here.
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
Locate the Privy integration guide and review its client configuration example, focusing on how the API key and RPC URL are described. Update the guide so the documented configuration matches the supported integration and no longer leads to the reported HTTP transport error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100