Hello Whats the approach for handling validation erros in ap

Question

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 lt String Any gt ` thinking face

mbonnin · Answer

Hi wave that s interesting do you have the returned json by any chance

Marco Pierucci · Answer

``` 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 · Answer

would this work

mbonnin · Answer

That helps

mbonnin · Answer

Let me check

mbonnin · Answer

Looks like you can get the errorClass with something like this ```response errors 0 extensions errorClass as String```

mbonnin · Answer

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 · Answer

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

Marco Pierucci · Answer

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 · Answer

Then you should be able to cast your way down ```response errors 0 extensions validationErrors as List lt Map lt String Any gt gt ```

mbonnin · Answer

``` response errors 0 extensions validationErrors as List lt Map lt String Any gt gt get 0 get message ```

Marco Pierucci · Answer

yeah exactly woudl this be the recommended way to go

mbonnin · Answer

Yep

Marco Pierucci · Answer

<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 · Answer

gt Martin Bonnin 4 28 PM gt Yep Ah ok

Marco Pierucci · Answer

well thanks then

mbonnin · Answer

I usually define helpers like this in my projects ```inline fun lt reified T gt Any cast = this as T val Any asMap Map lt String Any gt get = this cast val Any asList List lt Any gt 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 · Answer

This makes it easier to cast without breaking the flow

mbonnin · Answer

```response errors 0 extensions validationErrors asList 0 asMap message ```

mbonnin · Answer

gt 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 slightly smiling face It s all in extensions so it s all good

Marco Pierucci · Answer

yeah it looks better I guess

Marco Pierucci · Answer

cool thanks again

mbonnin · Answer

Sure thing