Add support for list input coercion x to [x] #5

Closed
opened 2023-08-23 23:24:04 +02:00 by ad-si · 3 comments

There is a (questionable) GraphQL feature which requires APIs to coerce single elements to lists of the element: https://spec.graphql.org/October2021/#sec-List.Input-Coercion

There is currently no way to implement this without patching graphql itself, right?

There is a (questionable) GraphQL feature which requires APIs to coerce single elements to lists of the element: https://spec.graphql.org/October2021/#sec-List.Input-Coercion There is currently no way to implement this without patching `graphql` itself, right?
Owner

It should already work, I implemented this feature and there is a unittest for input coercion that tests it. If there is a problem, it's a bug.

It should already work, I implemented this feature and there is a unittest for input coercion that tests it. If there is a problem, it's a bug.
Owner

If it really does not work, please provide a case that doesn't work and reopen the issue.

If it really does not work, please provide a case that doesn't work and reopen the issue.
belka closed this issue 2023-09-23 15:58:20 +02:00
belka added the
Kind
question
label 2023-09-23 15:59:11 +02:00
Contributor
@belka [I think this is where the error comes from](https://git.caraus.tech/OSS/graphql/src/commit/2fdf04f54a2d4fe68068ebeb232624e3dcce24b7/src/Language/GraphQL/Execute.hs#L574), although I might be wrong.
belka reopened this issue 2023-10-10 09:21:08 +02:00
belka closed this issue 2023-11-04 13:47:12 +01:00
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: OSS/graphql#5
No description provided.