Build declaratively back ends and APIs with GraphQL or REST
1–10 of 12 posts
Re: Build declaratively back ends and APIs with GraphQL or REST
#2This is nicely done. I like your marketing. I made it 98% of the way through reading your website, I was almost convinced. Then, I ran into a couple of typos right at the very end, that instead led to me writing you this comment on HN.
Re: Build declaratively back ends and APIs with GraphQL or REST
#3This promises the world but I had to work hard to find a code example, and even then I didn’t really “get” what the library will do for me in practice.
EDIT: after the pointer to the use cases in the thread below, I think I get it now! This seems like a great idea. Similar to Trustfall (rust) and GraphQLCompiler (Python).
I would be interested in using it if it was Typescript instead of Python. Still very cool how things snap together.
Re: Build declaratively back ends and APIs with GraphQL or REST
#4This promises the world but I had to work hard to find a code example, and even then I didn’t really “get” what the library will do for me in practice. EDIT: after the pointer to the use cases in the thread below, I think I get it now! This seems like a great idea. Similar to Trustfall (rust) and GraphQLCompiler (Python). I would be interested in using it if it was Typescript instead of Python. Still very cool how th…
There is a whole section with use cases and code examples on the website (crud, backend for frontend, function-as-a-service, iam provider and more): https://metatype.dev/use-cases/automatic-crud-validation
Re: Build declaratively back ends and APIs with GraphQL or REST
#5This is nicely done. I like your marketing. I made it 98% of the way through reading your website, I was almost convinced. Then, I ran into a couple of typos right at the very end, that instead led to me writing you this comment on HN.
There’s a typo in the HN title: “declaratively back ends”
Re: Build declaratively back ends and APIs with GraphQL or REST
#6This is nicely done. I like your marketing. I made it 98% of the way through reading your website, I was almost convinced. Then, I ran into a couple of typos right at the very end, that instead led to me writing you this comment on HN.
Thanks for the feedback, we are non-english speakers trying our best. Will review them soon.
Re: Build declaratively back ends and APIs with GraphQL or REST
#7This is nicely done. I like your marketing. I made it 98% of the way through reading your website, I was almost convinced. Then, I ran into a couple of typos right at the very end, that instead led to me writing you this comment on HN.
Thanks for the feedback, we are non-english speakers trying our best. Will review them soon.
As a non-native English speakers myself, ChatGPT has been a valuable tool. It's not about the small typos and errors (which tools like Grammarly could help), it's about the tone and everything.
Re: Build declaratively back ends and APIs with GraphQL or REST
#8This promises the world but I had to work hard to find a code example, and even then I didn’t really “get” what the library will do for me in practice. EDIT: after the pointer to the use cases in the thread below, I think I get it now! This seems like a great idea. Similar to Trustfall (rust) and GraphQLCompiler (Python). I would be interested in using it if it was Typescript instead of Python. Still very cool how th…
There is a whole section with use cases and code examples on the website (crud, backend for frontend, function-as-a-service, iam provider and more): https://metatype.dev/use-cases/automatic-crud-validation
In the example provided, the code uses Prisma. Am I missing something?
Re: Build declaratively back ends and APIs with GraphQL or REST
#9Earlier quoted context omitted.
There is a whole section with use cases and code examples on the website (crud, backend for frontend, function-as-a-service, iam provider and more): https://metatype.dev/use-cases/automatic-crud-validation
In the example provided, the code uses Prisma. Am I missing something?
Prisma is one of the runtime currently supported [1]. Metatype enables you to compose multiple runtimes together. Let's say you have model/struct product (id, name, similarProducts), the two first attributes may be stored in Prisma (like you would do it normally), the third one can come from another runtime such as an HTTP api and the engine will take care of resolving the data together. You can also add an authorization policy on any of the fields.
Re: Build declaratively back ends and APIs with GraphQL or REST
#10This is nicely done. I like your marketing. I made it 98% of the way through reading your website, I was almost convinced. Then, I ran into a couple of typos right at the very end, that instead led to me writing you this comment on HN.
There’s a typo in the HN title: “declaratively back ends”
yeah, I judged it poorly starting at the title