Derived JsonDecoder decodeJson vs fromJsonAST error inconsistency

[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".

I opened a PR with a test for this incosistency: #765.

[andreisilviudragnea]

@fsvehla

[YulawOne]

I came across a similar issue where an error doesn't make sense when decoded through AST:

case class Message(value: math.BigDecimal) derives JsonDecoder
val json = """{ "value": "" }"""

json.fromJson[Message]  == Left(".value(expected a 256 BigDecimal)")
json.fromJson[Json].flatMap(_.as[Message]) == Left("Unexpected end of input")