sangria-graphql/sangria

BLOCKING BUG: enum in case class fails with "Argument 'xyz' has invalid value: CNil"

Open

#528 opened on Nov 4, 2020

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Scala (1,961 stars) (219 forks)batch import
help wanted

Description

I have a case class which contains an enum for which I use EnumType()and deriveInputObjectType[] to create the schema.

Sangria shows an Argument 'testEnum' has invalid value: CNil when I send something like:

MethodCall(testCaseClass: {
    name: "just a name",
    testEnum: FIRST
  }) {
    result
  }

If I use testEnum as a parameter of a mutation directly, everything works fine. It seems that this problem only appears when an enum is used as part of a case class.

I am using Sangria 2.0.1, Circe 0.13.0 and Sangria-Circe 1.3.1

Contributor guide

Tech stack
scalagraphql
Domain
apibackend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
ScalaGraphQLSangria
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the deriveInputObjectType macro in Sangria (likely in InputTypeDerivation.scala) to understand how enum types are derived for case class fields. Compare with how enums are handled when used as direct mutation arguments. Check issues or comments for potential fixes or workarounds.