Towards Schemas end to end (without Effect)
Towards Schemas end to end (without Effect)
The dashboard knows the query type, but the output of a query is 'any'. Imagine that we document what is the type of output. The UI dev will be happier. And make it discoverable based on runs. Like how schema is generated now the from existing data in the db.
It would feel good to have some benefits of graphql (a contract between backend and front-end).
Frontend devs love to consume Graphql because the schema of the data is very clear.
So I am thinking two about two concepts:
- A. schemas for functions output (with errors and lifecycle status as data) like in go/elixir
- B. resolvers: for query implementation, so that we can say, it's more technical, it's using Promises, and it's ok to be more difficult.
A. is for product design days and UI
B. is for backend engineering days.
That's the DX i am thinking I would like to see.
The dashboard knows the query type, but the output of a query is 'any'. Imagine that we document what is the type of output. The UI dev will be happier. And make it discoverable based on runs. Like how schema is generated now the from existing data in the db.
It would feel good to have some benefits of graphql (a contract between backend and front-end).
Frontend devs love to consume Graphql because the schema of the data is very clear.
So I am thinking two about two concepts:
- A. schemas for functions output (with errors and lifecycle status as data) like in go/elixir
- B. resolvers: for query implementation, so that we can say, it's more technical, it's using Promises, and it's ok to be more difficult.
A. is for product design days and UI
B. is for backend engineering days.
That's the DX i am thinking I would like to see.
