pico-engine
pico-engine copied to clipboard
Picolab
An implementation of the pico-engine hosted on node.js
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.
Proposing a rule that selects on a `wrangler:new_key_value_pair` event, with attributes: `Id` the established subscription identifier, `key` a key not reserved* for subscriptions, and `value` an optional value (a falsy...
Any function in the did-o ruleset that modifies the pico-engine need to be reframed as a rule.
We've gotten along without this for some time, but when using a pico to host a web application it would be useful to know some more things about the HTTP...
Currently, rulesets import the did-o ruleset as didx to not conflict with the dido.ts . Maybe we should rename dido.ts to something else to avoid this conflict.
In the didtestdid test, the channels for the children need to be deleted when the children are deleted.
The title is odd, because GitHub is, above all else, a code repository. The awkwardness comes from: 1. We have to use the Raw version of a `krl` file, and...
An experiment on writing documentation about a KRL ruleset makes me wonder is some of it could be automatically generated from the source code (_à la_ `javadoc`). Example:
Phil [Today at 9:33 AM](https://picolabsio.slack.com/archives/C1BCUAPHR/p1666279989578399) Idea: foreign function interface in KRL so that rulesets can use JavaScript modules. Any exported function world be importable. (edited) :+1: 1 3 replies Phil...