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
At the moment we have CaseInsensitiveFieldAccessor which infers field existence of ViewableData and allows us to reference a urlSegment property in GraphQL, but read/write from URLSegment in the SS ORM.
This is naturally a bit of magic, but its too opaque by placing it in the field resolution. We should move this to the GraphQL type definition instead. This allows us to make mapping choices more explicit.
**Subtask of silverstripe/silverstripe-asset-admin#316 **
At the moment we have CaseInsensitiveFieldAccessor which infers field existence of
ViewableData
and allows us to reference aurlSegment
property in GraphQL, but read/write fromURLSegment
in the SS ORM.This is naturally a bit of magic, but its too opaque by placing it in the field resolution. We should move this to the GraphQL type definition instead. This allows us to make mapping choices more explicit.
Rough API sketch:
TODO Figure out how to retain mapping for query resolvers
This is also required for the type scaffolding
The text was updated successfully, but these errors were encountered: