top | item 40984046 (no title) brobdingnag_pp | 1 year ago Why do you mention GraphQL and JSON:API in the same sentence? The latter is at least 10x more difficult to understand with all its edge cases around entity relations and filtering. discuss order hn newest megadal|1 year ago > Why do you mention GraphQL and JSON:API in the same sentence?I usually tend to use words like these in sentences wherein there are phrases or clauses in which those words are the subject.In all seriousness though, I mentioned JSON:API because it is a standard one can easily Google and it is a graph based data access API.I wanted to demonstrate that it was possible for GraphQL to have been RESTful with the same ontology and mechanics.I couldn't care less if someone created a JSON:API fork that handled relations like GraphQL, it would still be heavily preferred to GraphQL.Also, the format for filtering in JSON:API is not defined by the spec. In other words, you can write whatever wacky query language you want.
megadal|1 year ago > Why do you mention GraphQL and JSON:API in the same sentence?I usually tend to use words like these in sentences wherein there are phrases or clauses in which those words are the subject.In all seriousness though, I mentioned JSON:API because it is a standard one can easily Google and it is a graph based data access API.I wanted to demonstrate that it was possible for GraphQL to have been RESTful with the same ontology and mechanics.I couldn't care less if someone created a JSON:API fork that handled relations like GraphQL, it would still be heavily preferred to GraphQL.Also, the format for filtering in JSON:API is not defined by the spec. In other words, you can write whatever wacky query language you want.
megadal|1 year ago
I usually tend to use words like these in sentences wherein there are phrases or clauses in which those words are the subject.
In all seriousness though, I mentioned JSON:API because it is a standard one can easily Google and it is a graph based data access API.
I wanted to demonstrate that it was possible for GraphQL to have been RESTful with the same ontology and mechanics.
I couldn't care less if someone created a JSON:API fork that handled relations like GraphQL, it would still be heavily preferred to GraphQL.
Also, the format for filtering in JSON:API is not defined by the spec. In other words, you can write whatever wacky query language you want.