add Check command to check if a component is compatible with edgee

[CLEMENTINATOR]

Checklist

• I have read the Contributor Guide
• I have read and agree to the Code of Conduct
• I have added a description of my changes and why I'd like them included in the section below

@KokaKiwi it is set to merge into your branch

[CLEMENTINATOR]

tested with rs component

╭─clement@brittle-hollow ~/work/components/example-rs-component ‹initial_import●›
╰─$ ../../edgee/target/debug/edgee components check
╭─clement@brittle-hollow ~/work/components/example-rs-component ‹initial_import●›
╰─$ ../../edgee/target/debug/edgee components check -c target/wasm32-wasip2/release/example_rs_component.wasm
Error: no exported instance named `edgee:protocols/consent-mapping`
╭─clement@brittle-hollow ~/work/components/example-rs-component ‹initial_import●›
╰─$ ../../edgee/target/debug/edgee components check -d target/wasm32-wasip2/release/example_rs_component.wasm                                                                                                           

[alexcasalboni]

Imho, the Error: no exported instance named edgee:protocols/consent-mapping error is very confusing and we should try to wrap the runtime errors into understandable messages like "Component not found", "Component not valid", "Invalid component type", "Component is valid", etc.

Also, would it be possible to infer the component type (data collection, consent mapping, etc.) without specifying it with -c or -d? That would make it much easier to use.

[CLEMENTINATOR]

Imho, the Error: no exported instance named edgee:protocols/consent-mapping error is very confusing and we should try to wrap the runtime errors into understandable messages like "Component not found", "Component not valid", "Invalid component type", "Component is valid", etc.

Also, would it be possible to infer the component type (data collection, consent mapping, etc.) without specifying it with -c or -d? That would make it much easier to use.

I'll wrap the errors !

Regarding the second question, I am not sure that we can detect the component type (directly from a wasm file i mean).

[alexcasalboni]

Regarding the second question, I am not sure that we can detect the component type (directly from a wasm file i mean).

We should be able to inspect the interface and check what it's export. Something like this:

wasm-tools component wit component.wasm

At some point the output should contain

package edgee:protocols {
    interface data-collection {
        ...
        page: func(e: event, cred: dict) -> result<edgee-request, string>;
        track: func(e: event, cred: dict) -> result<edgee-request, string>;
        user: func(e: event, cred: dict) -> result<edgee-request, string>;
    }
}

[CLEMENTINATOR]

Regarding the second question, I am not sure that we can detect the component type (directly from a wasm file i mean).

We should be able to inspect the interface and check what it's export. Something like this:

wasm-tools component wit component.wasm

At some point the output should contain

package edgee:protocols {
    interface data-collection {
        ...
        page: func(e: event, cred: dict) -> result<edgee-request, string>;
        track: func(e: event, cred: dict) -> result<edgee-request, string>;
        user: func(e: event, cred: dict) -> result<edgee-request, string>;
    }
}

For me, this tool checks that the component implements a given world (and not the world that is in the component itself)

Eg if an user creates a cmp component, and defines it as a data-collection component in the registry, the tool should check the component against the data-collection component type and not the cmp component type (the one that is detected by wasm tools component wit)

[alexcasalboni]

I think this command isn't going to be used by OSS developers too often and we probably want to automatically run it before edgee component push to make sure the .wasm file is valid before uploading it.

[CLEMENTINATOR]

I think this command isn't going to be used by OSS developers too often and we probably want to automatically run it before edgee component push to make sure the .wasm file is valid before uploading it.

Exactly, its to precheck on the client side before we check it ourself on server side !