Derived JsonDecoder decodeJson vs fromJsonAST error inconsistency tests

[andreisilviudragnea]

JsonDecoder {
  final def decodeJson(str: CharSequence): Either[String, A]
  def fromJsonAST(json: Json): Either[String, A]
}

• Derived JsonDecoders have different errors for:
  • missing fields when calling JsonDecoder.decodeJson (".b.c.v2(missing)") vs JsonDecoder.fromJsonAST ("Missing fields: v2, v3")
  • invalid types when calling JsonDecoder.decodeJson (".b.c.v1(expected '\"' got '1')") vs JsonDecoder.fromJsonAST ("Not a string value").
• The errors reported by JsonDecoder.fromJsonAST seem to be broken because the JSON path to the error is missing from the messages: "Missing fields: v2, v3", "Not a string value".

Scala 3 derived decoders fail at runtime with StackOverflowError for now. This might be another bug.

[CLAassistant]

All committers have signed the CLA.

[andreisilviudragnea]

@fsvehla There seems to be a StackOverflowError problem when running the tests on Scala 3, but I am interested at the moment on the Scala 2 implementation.

Scala 3 decoder generation is different from Scala 2, so I think I might have found another bug or maybe the test is not written in the right file.