It would be really helpful if you could document how to do the following with ic-kit:

• dynamic canister creation
• automatic Candid generation
• inter canister calls

as comments in the examples provided and provide any guidance on how to set it up from scratch on a new project.

I was using ic-kit 0.4.8 before. It included calls to the management canister as documented here for the dynamic creations of canisters but that seems to have been removed in v0.5 onwards.

And I had been using the cargo test mechanism of automatic Candid generation as used in some other Psychedelic projects like this

For inter canister calls, I tried the mechanism outlined here but it's not type safe so it breaks compilation with Cargo. I created a post for it here

I feel ic-kit 0.5 would probably solve all of the above but I'm unable to make it work atm.

I see some of the examples have pending todos and I imagine you'll be fleshing them out in more details.

In case you already plan to cover the above, please ignore this issue :)

I found that ic_cdk 0.4.0 deprecate block_on function and use its own spawn.

ic_kit use ic_cdk::block_on to do the job of ic::spwan.

Besides, ic_cdk::spawn doesn't need Send trait bound to the future F while ic_kit does.

#[inline(always)]
pub fn spawn<F: 'static + std::future::Future<Output = ()> + std::marker::Send>(future: F) {
    get_context().spawn(future)
}

When I have a job which call another canister, the future returned does not have Send trait. Thus ic::spawn can not execute the job.

    |
498 |     let xtc_balance: (Nat, ) = ic::call(Principal::from_text(XTC).unwrap(), "balanceOf", (ic::id(),))
    |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ await occurs here on type `Pin<Box<dyn Future<Output = Result<(ic_kit::candid::Nat,), (RejectionCode, std::string::String)>>>>`, which is not `Send`
note: required by a bound in `ic_kit::ic::spawn`


    |
555 |     ic::spawn(schedule_job());
    |     ^^^^^^^^^ future returned by `schedule_job` is not `Send`
    |

this removes user-level dependency on ic-cdk, the macro is currently a copy of ic-cdk's but at least now it's in our repo so we can start being innovative on top of it.

This implements and adds the ic-kit-sys crate, which is a low-level binding to the IC and provides us with a nicer level of abstraction that will be used to simplify the code for ic-kit.

Adds HTTP routing to kit canisters!

Currently, the functionality is provided as a flag on ic-kit, and will enable the required features in the kit macros.

Example

An example HTTP pastebin is provided in the examples

use ic_kit::prelude::*;

#[get(route = "/")]
fn index_handler(_: HttpRequest, _: Params) -> HttpResponse {
    HttpResponse {
        status_code: 200,
        headers: vec![],
        body: b"this is an example".into(),
        streaming_strategy: None,
        upgrade: false,
    }
}

How it works?

Internally, for the routing, we use matchit, a blazing fast URL router. Routing happens within the nanosecond scale :) This is the same library used for cloudflare/worker-rs

Tasks

• [x] initial implementation (get only)
• [x] Support all HTTP methods (get, put, post, options, head, patch, delete, connect)
• [x] simple pastebin example (basic usage + canister side rendering)
• [x] Helper for getting a specific header field from an HttpRequest
• [x] Helpers for building an HttpResponse
• [x] DI support (integrate into existing entrypoint instead of custom)
• [ ] graceful error macros + routing (handlers should return Results, catch error and route accordingly)

This implements the management canister with a custom ic_kit_install method. The final result should be having the ability to dynamically install typed canisters both in the kit-runtime and to make it work in the IC env as well.

#[derive(KitCanister)]
#[candid_path("candid.did")]
#[wasm_path("canister.wasm")]
pub struct CounterCanister;

And a factory canister should now be able to deploy this canister on the fly by doing:

use counter_canister::CounterCanister;

#[update]
fn deploy_canister(canister_id: Principal) {
  CounterCanister::install_code(canister_id, InstallConfig {...}).await;
}

The install_code implementation should use different targets #[cfg(not(target_family = "wasm"))] and #[cfg(target_family = "wasm")] to perform platform specific calls to the management canister.

Hi. Amazing library! Can you please provide some insight on how to mock a canister with existing methods.

Say, I have a method

#[update]
async fn do_nothing(my_arg: u64) -> Result<(), String> {
    Ok(())
}

How would I create a Canister mock with the method above? I've tried to use RawHandler, but cannot figure out how to transfer arguments correctly.

The way I want to use it later is like so:

let canister = Canister::new(mock_principals::alice())
    .method("do_nothing", ...);

let ctx = canister.context().inject();
ic::call_with_payment(mock_principals::alice(), "do_nothing", (1000), 100);

Is it even possible with the current implementation?