You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've found that the API returns any numeric string as a JSON integer if there are no non-numeric characters, it doesn't start with 0, and its value is 2137483646 or lower. Can't remember what the deal is with negative numeric strings or decimals.
So until the API returns JSON types in line with the DB types, beware that either strings or integers may be returned for almost any field.
Gotcha, thanks @jtc . The second screenshot is from the documentation on Github. I've already changed our code to treat it like a String instead of an Integer but figured I'd mention as the pojos were generated based on the example json ( https://github.com/TheAlphaSchoolSystemPTYLTD/employee-hr/blob/master/getEmployeesDetails.md - Success Response) and others may come across this.
The API defines this as an integer however it seems that one of our client schools is able to enter 'TBA' into the postcode field.
This causes our JSON parsing to break. An easy fix fortunately but thought I'd mention.
The text was updated successfully, but these errors were encountered: