Thanks, that makes sense. Does it necessitate a Dart frontend? It looks like the client-side is code-generated, but is the API usable without code-generation, does it present a nice API model, or is it heavily dependent on the assumption that a first-party code-generated client is being used?
Yes, it is using well-formed JSON and/or web sockets. Serialization is following the Dart standard, and you can use it together with popular Dart serialization packages, such as Freezed.
However, we are still working on making the documentation for APIs. That is on the roadmap as well as providing code generation for other languages.
Comments
Thanks, that makes sense. Does it necessitate a Dart frontend? It looks like the client-side is code-generated, but is the API usable without code-generation, does it present a nice API model, or is it heavily dependent on the assumption that a first-party code-generated client is being used?
Yes, it is using well-formed JSON and/or web sockets. Serialization is following the Dart standard, and you can use it together with popular Dart serialization packages, such as Freezed.
However, we are still working on making the documentation for APIs. That is on the roadmap as well as providing code generation for other languages.