Content
@
https://warpcast.com/~/channel/sys
0 reply
0 recast
0 reaction
Phil Cockfield
@pjc
2 replies
0 recast
5 reactions
Rafi
@rafi
Does it use automerge repo?
1 reply
0 recast
1 reaction
Phil Cockfield
@pjc
GM @rafi ð It does indeed - I'm rewriting a tight little `Immutable<T>` shim over the 2.0 repease or `automerge-repo` - alot of tight cleanup seems to have gone on in this milestone.
1 reply
0 recast
0 reaction
Phil Cockfield
@pjc
Trying to get this as minimal LoCs as possible spin up. The Immutable<T> (observable) interface is the generic interface I have over a bunch of different persistence mechanisms - and so far seems to be playing quite nicely as a simple/portable concept of the "cluster fuck" which generally is "state" ð±
1 reply
0 recast
0 reaction
Phil Cockfield
@pjc
This <Input.DocumentId> stateful component is intended as a compact UI unit to do the same thing as code above - namely "one line" drop in for spinning up and addressing documents out of a repo. Next steps: - bind to a RichText editor (ProseMirror) - bind to Monaco (VSCode code editor) 𧫠text.splice
1 reply
0 recast
1 reaction
Phil Cockfield
@pjc
There are some nice looking hooks emerging in `repo` around encryption and ACL which I'm keeping my ðïž on.
2 replies
0 recast
2 reactions
Phil Cockfield
@pjc
DevHarness (WIP): https://fs.db.team/sys/ui.driver.automerge/ https://fs.db.team/sys/ui.driver.automerge/?dev=5578674644815
1 reply
0 recast
0 reaction
Phil Cockfield
@pjc
ref: Immutable<T> https://jsr.io/@sys/types/0.0.102/src/types/t.Immutable.ts
1 reply
0 recast
0 reaction
Rafi
@rafi
That's a very comprehensive system. What are you using it for?
0 reply
0 recast
0 reaction
