You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is to be a space to discussion the current Arri App Definition and Arri Type Definition specifications. I really want to lock this down as it will be used as the intermediate representation of applications across all languages. Any feedback is welcome.
In my view these documents should:
make it easy to generate type-safe clients
be easy to auto-generate from code
have consistent syntax
Non-goals:
make it easy to be hand written by humans (it's okay if this happens as a side-affect I suppose)
It'd also like to explore what adding support from non-http transport would look like. Currently these assume assume a request response model, however this isn't the case with all applications. Realtime apps using something like websockets may just be designed in a send and forget way. What would representing something like that look like? If we want to support it.
References to the current specifications can be found here:
This issue is to be a space to discussion the current Arri App Definition and Arri Type Definition specifications. I really want to lock this down as it will be used as the intermediate representation of applications across all languages. Any feedback is welcome.
In my view these documents should:
Non-goals:
It'd also like to explore what adding support from non-http transport would look like. Currently these assume assume a request response model, however this isn't the case with all applications. Realtime apps using something like websockets may just be designed in a send and forget way. What would representing something like that look like? If we want to support it.
References to the current specifications can be found here:
Ideally this is something that once finalized never changes. So we should really take time to consider all the use cases we want to support.
The text was updated successfully, but these errors were encountered: