Bruce Conrad
Bruce Conrad
This is to follow up on issue #568 when flushing a ruleset in the UI, and the ruleset compiles (and so can be registered with the pico-engine) but cannot be...
This is a bootstrapping issue, having to do with these two rulesets: ``` io.picolabs.pico-engine-ui io.picolabs.wrangler ``` The version 1 pico engine came with just the first of these, and we...
When creating a channel (`ctx:newChannel` (called by `wrangler:createChannel`)) one of the parameters is an array of strings used as tags. Each tag is sanitized, to replace runs of special characters...
This seems to invoke the parsing for the content types that we need for DIDComm v2.
For interoperating with other DIDComm v2 systems that use, for example ``` "content-type": "application/didcomm-encrypted+json", ``` which the pico engine currently doesn't support. Since we wish to support DIDComm v2, we...
Phil reported: > I have a rule that accepts an event attribute that is an identifier but looks like an 18-digit number. Like this: 830010923977419046. When I look in the...
We need the `dido` library to raise an event at the moment when a DID exchange results in a connection being established. This needs to happen both for the pico...
The `provides` directive identifies functions in a ruleset that can be used by other rulesets using this one as a module. The `shares` directive identifies functions that can be invoked...
There needs to be a way to clean them up, without just [removing them all](https://github.com/Picolab/pico-engine/blob/master/packages/pico-engine/krl/io.picolabs.did-o.krl#L119-L124), which is the only option available now.
As an enhancement, we might want invitations that can be used more than once.