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
Hello maintainers
As a part of research around the simplifying graphql spec tests across implementations, I've stumbled upon the specs written here for sangria. I'd really appreciate if I can get an idea around how difficult it has been to maintain this test suite, and how often does it go out of parity with the actual graphql spec? Were there cases when misunderstanding the spec led to issues with the library?
Would having a generic set of compatibility tests help around these issues if any?
As schema definition in SDL format is natively supported by the library then it would be easy to adapt generic testing suite across different languages.
The text was updated successfully, but these errors were encountered:
Edit
Spec discussion -> graphql/graphql-spec#698
Hello maintainers
As a part of research around the simplifying graphql spec tests across implementations, I've stumbled upon the specs written here for
sangria
. I'd really appreciate if I can get an idea around how difficult it has been to maintain this test suite, and how often does it go out of parity with the actual graphql spec? Were there cases when misunderstanding the spec led to issues with the library?Would having a generic set of compatibility tests help around these issues if any?
As schema definition in SDL format is natively supported by the library then it would be easy to adapt generic testing suite across different languages.
The text was updated successfully, but these errors were encountered: