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
This is not really a feature request, but I suggestion to avoid a wide category of bugs. But it would also wastly simplify extending graphql request.
at the moment, unchained still uses hand-written schemas and resolvers. This approach is not sound (type safe) and can lead to bugs like #525 or any other type-missmatch.
There are good "code-first" approaches to write graphql. Unfortunatly many of those are not created with 100% type-safety in mind. An exception is https://pothos-graphql.dev/
Pothos has a builder api and can actually guarantee type-safety on arguments and resolvers, including proper null/non-null checks (if strict mode is on, which is mandatory for any library/framework imho).
Additionaly, unchained could wrap and expose pothos api to projects using unchained which would wastly simplify extendig the graphql-api of unchained and enforce correctness.
The text was updated successfully, but these errors were encountered:
This is not really a feature request, but I suggestion to avoid a wide category of bugs. But it would also wastly simplify extending graphql request.
at the moment, unchained still uses hand-written schemas and resolvers. This approach is not sound (type safe) and can lead to bugs like #525 or any other type-missmatch.
There are good "code-first" approaches to write graphql. Unfortunatly many of those are not created with 100% type-safety in mind. An exception is https://pothos-graphql.dev/
Pothos has a builder api and can actually guarantee type-safety on arguments and resolvers, including proper null/non-null checks (if strict mode is on, which is mandatory for any library/framework imho).
Additionaly, unchained could wrap and expose pothos api to projects using unchained which would wastly simplify extendig the graphql-api of unchained and enforce correctness.
The text was updated successfully, but these errors were encountered: