Enums in arguments are serialized in quotes

When there is an enum in query inlined arguments it is serialized as a string in quotes. See the following example - the alignment input field is an enum field.

Current request:

mutation {
        someMutation(
                update: {alignment: "left"}
        ) {
                ok
                errorMessage
        }
}

Expected request:

mutation {
        someMutation(
                update: {alignment: left}
        ) {
                ok
                errorMessage
        }
}

I can work around it by sending the arguments in variables, but that’s not ideal for my use case.

[babyfish-ct]

Different from the parameters of variables-style, inline-style parameters are not developed based on the type system (This problem was thought about when the project is created, and the reason why it was not dealt with is because inline-style is not the main design goal).

To fix this flaw, a major refactoring would have to be done to make inline-style parameters based on type information instead of plain JSON, so that the system can distinguish between strings and enums.

So, it’s a huge task and can’t be achieved in the short term.

The variables-style is better than the inline-style, and almost all frameworks recommend the variable-style.

However, your answer surprised me, what particular scenario leads you to think inline-style is better? Could you share your scenario and your thoughts?. maybe there is a better way.

[babyfish-ct]

Because 3.1.3 or 3.1.4 fixed it.

Later, 3.1.5 will be released.