#frontend API

1 messages · Page 1 of 1 (latest)

vestal wraith
#

will jump into this tomorrow! initial read on it: our current "frontend API" is largely spans + span attributes, which works great technically but the DX feels like a third rail. it would be great to have a high level API instead with whatever UI hints users need.

the hard part is getting it to work transparently with OTel in each target language. if I start a span with Dagger's API, and beneath that span run something that's integrated with OTel, those spans need to be children of the Dagger-created span. but, maybe we can have some sort of special type that SDKs handle. thinkspin

also: if you have the time, a wireframe/mock of how you really want it to look in the end would be a great jumping off point, to see how it could be modeled

ashen mortar