Refactor the call API (breaking changes)

[lastmjs]

Contributor

• Code has been declaratized
• All new functions have JSDoc/Rustdoc comments
• Error handling beautiful (no unwraps or expects etc)
• Code tested thoroughly
• PR title:
  • Indicates breaking changes with suffix "(breaking changes)"
  • Sentence cased
• Related issues have been linked and all tasks have been completed or made into separate issues
• New documentation enumerated in the release issue
• All breaking changes
  • Described below in the "Breaking Changes" section
  • Migration path described

Reviewer

• Code has been declaratized
• All new functions have JSDoc/Rustdoc comments
• Error handling beautiful (no unwraps or expects etc)
• Code tested thoroughly
  • Pull rejection code out of CanisterResult err #446 has been at least tested manually
• PR title:
  • Indicates breaking changes with suffix "(breaking changes)"
  • Sentence cased
• Related issues have been linked and all tasks have been completed or made into separate issues
• New documentation enumerated in the release issue
• All breaking changes
  • Described below in the "Breaking Changes" section
  • Migration path described
• Read this entire section in The Interface Spec, deeply considering if we have covered everything: https://internetcomputer.org/docs/current/references/ic-interface-spec#system-api-call
• Review the entire call API on the next branch of the Rust CDK, deeply considering if we have covered everything and if our API is good: https://github.com/dfinity/cdk-rs/blob/next/ic-cdk/src/call.rs

Breaking Changes

call has had a number of fundamental changes made to it.

The raw property is now a boolean, and simply toggles encoding of the arguments and decoding of the return value. If raw is true, the args property should be a Uint8Array. Omitting args or passing in undefined when raw is set to true will automatically Candid encode the empty argument.

We have also removed the notify function. call now has a oneway property that if set to true will immediately resolve the promise and return void.

The error thrown from an unsuccessful call now has a slightly different message.