This repository has been archived by the owner on Oct 7, 2024. It is now read-only.
fix: allow the request ID to be a string, number or null #156
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.
Description
The current API forces the ID of the JSON-RPC requests to be a UUIDv4, which is not compliant with the official JSON-RPC specs. Note, however, that this constraint doesn't have an impact on devs who use the Keyring clients, such as
KeyringSnapRpcClient
andKeyringSnapControllerClient
.This PR removes this limitation and allows the request ID to be any string, number or null.
Related issues
Fixes #154