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 just popped up because I knew I'd seen something about automatic types being generated for resources with metadata, but couldn't find it in the docs - so I looked in the source.
Resources that use the AshGraphql.Resource extension get verifiers applied to them, one of which is AshGraphql.Resource.Verifiers.VerifyQueryMetadata. This verifies that if a query action has metadata defined and shown in the response, a custom type must be defined for the response (eg. :user_with_token).
These verifiers do not apply to queries defined on a domain, so any metadata will silently be ignored and dropped.
Expected behavior
The same error that is generated for queries on resources should also be generated for queries on domains.
Runtime
Elixir version 1.17.3-otp-27
Erlang version 27.1
OS macOS Sonoma
Ash version 3.4.42
AshGraphql 1.4.3
The text was updated successfully, but these errors were encountered:
Describe the bug
This just popped up because I knew I'd seen something about automatic types being generated for resources with metadata, but couldn't find it in the docs - so I looked in the source.
Resources that use the
AshGraphql.Resource
extension get verifiers applied to them, one of which isAshGraphql.Resource.Verifiers.VerifyQueryMetadata
. This verifies that if a query action has metadata defined and shown in the response, a custom type must be defined for the response (eg.:user_with_token
).These verifiers do not apply to queries defined on a domain, so any metadata will silently be ignored and dropped.
Expected behavior
The same error that is generated for queries on resources should also be generated for queries on domains.
Runtime
The text was updated successfully, but these errors were encountered: