* First pass at custom coerce for input objects

[njlr]

No description provided.

[xperiandri]

I like what you have done. This is useful.
Also, it would be more useful to be able to return an error and pass that error to the response with error to GraphQL field mapping.

[xperiandri]

Suggested change

	|>Array.map (fun field ->
	letvalueFound= Map.tryFind field.Name map|> Option.toObj
	letcoercedValue= coerceVariableValue false field.TypeDef vardef valueFound (errMsg +(sprintf "in field '%s': " field.Name))
	|>Seq.map (fun field ->
	letvalueFound=map |>Map.tryFind field.Name |> Option.toObj
	letcoercedValue= coerceVariableValue false field.TypeDef vardef valueFound (errMsg +(sprintf "in field '%s': " field.Name))

Maybe it does not worth to materialize it to an array

[xperiandri]

@jberzy can we switch this to Result<,> and pass an error to the response?

[xperiandri]

There is an issue I have with current scalar implementation

interface ScalarDef withmemberx.Name= x.Name
memberx.Description= x.Description
memberx.CoerceInput input = x.CoerceInput input |> Option.map box
memberx.CoerceValue value =(x.CoerceValue value)|> Option.map box

This piece is very contraintuitive

memberx.CoerceInput input = x.CoerceInput input |> Option.map box
memberx.CoerceValue value =(x.CoerceValue value)|> Option.map box

@jberzy at least XML comments with clear description required.
Can we get rid of CoerceValue at all?

And CoerceInput here may be optional. Because if I preprocess variables with JSON deserializer I don't need any coercion at all.

[njlr]

@xperiandri I have fleshed out this idea further: #351