Hello! Whats the approach for handling validation ...

# apollo-kotlin

[Marco Pierucci]

Hello! Whats the approach for handling validation erros in apollo kotlin?
I used to catch refresh token issues in customAttributes
Now Im trying to update to apollo 3.4 and switched to nonStandardFields as suggested.

But now when getting refresh token errors, nonStandardFields come as null and the actual erros come as:

extensions = {errorClass=VALIDATION, validationErrors=[{message=Please make sure the refresh token is correct., inputPath=[input, input]}]}

extension being : Map<String, Any?>? 🤔

[mbonnin]

Hi 👋 that's interesting! do you have the returned json by any chance?

[Marco Pierucci]

NetworkException(errors=[Error(message = Invalid data, locations = [Location(line = 1, column = 65)], path=[obtainCoconutToken], extensions = {errorClass=VALIDATION, validationErrors=[{message=Please make sure the refresh token is correct., inputPath=[input, input]}]}, nonStandardFields = null)])

[Marco Pierucci]

would this work?

[mbonnin]

That helps!

[mbonnin]

Let me check

[mbonnin]

Looks like you can get the errorClass with something like this:

response.errors[0].extensions["errorClass"] as? String

[mbonnin]

More recent versions of the spec now support "extensions". I guess this is why Apollo 2 didn't have support for this: https://spec.graphql.org/draft/#sel-GAPHRPfCCBCEoD2xG

[Marco Pierucci]

Yeah that gives me the error class, but what about If I need to get the validationErrors message

[Marco Pierucci]

Feels like it can become quite convoluted ( and am also tied to a string errorClass or validationsError that could easily change on an update an break my app?

[mbonnin]

Then you should be able to "cast" your way down:

response.errors[0].extensions["validationErrors"] as? List<Map<String, Any?>>

[mbonnin]

(response.errors[0].extensions["validationErrors"] as? List<Map<String, Any?>>).get(0).get("message")

[Marco Pierucci]

yeah exactly, woudl this be the recommended way to go?

[mbonnin]

Yep.

[Marco Pierucci]

https://github.com/apollographql/apollo-kotlin/issues/1964
I know its not the same but on apollo 2 and before seems like we could look for it in customAttributes so maybe it should be showing in non standardFields on 3.x and above?

[Marco Pierucci]

Martin Bonnin [4:28 PM]

Yep.

Ah ok

[Marco Pierucci]

well thanks then

[mbonnin]

I usually define helpers like this in my projects

inline fun <reified T> Any?.cast() = this as T

val Any?.asMap: Map<String, Any?>
  get() = this.cast()
val Any?.asList: List<Any?>
  get() = this.cast()
val Any?.asString: String
  get() = this.cast()
val Any?.asBoolean: String
  get() = this.cast()
val Any?.asNumber: Number
  get() = this.cast()

[mbonnin]

This makes it easier to cast without breaking the flow

[mbonnin]

response.errors[0].extensions["validationErrors"].asList[0].asMap["message"]

[mbonnin]

I know its not the same but on apollo 2 and before seems like we could look for it in customAttributes so maybe it should be showing in non standardFields on 3.x and above?

The ways your server answers is actually standard 🙂 . It's all in "extensions" so it's all good

[Marco Pierucci]

yeah it looks better I guess

[Marco Pierucci]

cool thanks again!

[mbonnin]

Sure thing!