Joe
Joe
Thanks @gobwas This helped me with my wrapper https://github.com/joeblew999/goPocJsonSchemaForm/blob/main/handler/schemaHandler.go
Adding myself as I also need this
Ahh interesting I have used Process-compose ( https://github.com/F1bonacc1/process-compose ) and task. They both use the exact same way to describe variables. EX: https://github.com/F1bonacc1/process-compose/blob/main/process-compose.yaml#L123C9-L123C13 ```sh {{.VAR_NAME}} ``` It's not really like...
you could do that. but benthos is designed to do this. you can use task with benthos, so why not ?
Totally understand you pov . Let’s just decide if we want to add tab completions ?
> [@gedw99](https://github.com/gedw99) This library doesn't do any networking, so you should probably do that in a wrapping layer. 100% agree that the wrapping golang package is the place to do...
I think that it might be a lot easier to compile the auto merge rust to WASM and then use Wazero to call it. it will not be quiet as...
5 seconds I just wrote a wrapper layer https://github.com/joeblew999/automerge-wazero-example Not all of the rust automerge is wrapped yet with tests. About 60% there
its up to 80% coverage now. Allows editing in the browser or server. using datastar-go for the synchronisation of the WebGUi or TUI
> Yes, I saw your project! > > 5s is a long time – but I do like the idea of wazero in principle (cross compilation is a pain right...