In recent versions of Demand Control, the runtime supports nested keys. To get there, we must go through compostion first, but using something like that fails:
type Query {
search(input: SearchInput!): [Book]
@listSize(slicingArguments: ["input.pagination.first"], requireOneSlicingArgument: true)
}
Due to the fact that our composition assumes that slicingArguments field must point to a single-named field "input.pagination.first" instead of checking the nested keys in the input types.
In recent versions of Demand Control, the runtime supports nested keys. To get there, we must go through compostion first, but using something like that fails:
Due to the fact that our composition assumes that
slicingArgumentsfield must point to a single-named field"input.pagination.first"instead of checking the nested keys in the input types.