The HTTP Query Spec has a `Token` value in it that needs to be either generic or `any`
Open
@chenyan-dfinity is already working on this.
Since Mar 17, 2021.
enhancement
- Dominant language
- Rust
- Stars
- 301
- Forks
- 85
- Avg merge
- 1h 4m
- Merged PRs (30d)
- 4
Description
From the point of view of the spec, this field's type does not matter; whatever the canister returns we send back in the same shape. But from the Candid file documenting the HTTP Query spec, it becomes a simple record {} because there's no way to communicate this properly in Candid.
Either Candid could implement a generic (in which case the token becomes T) or the any type, as the token could change type between two responses (and the spec does not actually care).
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.
Assessment
This issue has not been assessed yet.