0.9 discussion 💖

[jem-computer]

Hey all!
A2UI is SO rad, I haven't been excited about technology like this in a reallll long time, gg :)

I would love have an open communication channel with the folks behind `0.9:

1. are y'all set on the refactored spec as it's defined in specifications/0.9 going forward (for now!), or is it still in flux? I can live on the edge I just wanna make sure I'm not chasing the wrong thing
2. any thoughts on building out ecosystem tooling for 0.8 vs getting ahead of the changes and going with 0.9? I'm working on a React implementation and design tooling rn :)))

cc @gspencergoog @jacobsimionato + referencing #226

[gspencergoog]

We're glad you're excited about it!

No, 0.9 hasn't been set yet: we're planning on doing some review and refining in the new year.

Excellent that you're interested in a React implementation! I think as an experimental spec, it might be premature to build a lot of tooling around 0.8, since (as you can see) it is about to change drastically in 0.9. But as long as you know that up front, feel free to make what you're comfortable with.

We haven't yet finished the formal review, or even had a lot of debate yet, around 0.9, so it might still change quite a bit. If I were to "read the weather" around it, I'd say there's some interest in revising the data model some more, and perhaps some theming work to be done. In general, the approach of moving away from structured output to a more readable and modular schema has been well received.

[almandsky]

It is great to see the improvement in the v0.9 version. It will optimize for the LLM generation, and easier to handle the life-cycle of the component rendering in the clide-side.

https://a2ui.org/specification/v0.9-a2ui/#updatecomponents

op (string, optional): The operation to perform on the data model. Must be 'add', 'replace' or 'remove'. If omitted, defaults to 'replace'.

upsert maybe more simple than add and replace. The client can just update the component rendering if it already exists. The server side no need to keep track if the component state.

[wrenj]

@gspencergoog @jacobsimionato

Can we use JSON merge patch instead of JSON patch for updateData and updateComponents:
https://zuplo.com/learning-center/what-is-json-merge-patch

It will be simpler (no "op", no need for a list of "op") and less error prone (no key errors from client/server datamodels being out of sync, since everything is an upsert/remove if present). The only restriction is key=null means delete key which is probably a nice simplification anyway.