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
Hi, this is a very interesting project! There might be options to piggyback on developments around generators:
The way graphql-code-generator generates typings/queries/hooks and what not is either by a schema file or a live endpoint's introspection. If it's possible to generate an introspection for a sparql endpoint, all existing generators could use that in turn. Here's a generator for an introspection file
Another problem is very custom graphql endpoints, often with different maturity levels of individual queries and mutations.
I believe in order to get people to use global identifiers, their domain model has to have some translation/transformation to global models as well. Graphql in practice is often used like REST, and often tree models instead of graphs, especially towards the beginning of projects. To keep a graph database's model and a graphql schema in sync, there's a project from neo4j that generates the graph's relationships as a result of a graphql schema with annotations. Maybe this can help conceptually, here's how relationships are expressed there, queries and mutations are auto-generated and resemble their query language.
When given a GraphQL-LD query, it should be possible to auto-generate TypeScript typings.
For example:
Example of typings:
The text was updated successfully, but these errors were encountered: