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
Currently com.bunq.sdk.model.generated.object.Geolocation has three BigDecimal fields. However, there seems to be a mismatch. If you take a look at com.bunq.sdk.json.BigDecimalTypeAdapter it reads a BigDecimal from type String. Yet the api returns a value of type number.
I did not make the pull request myself because I don't know which fix you'd like me to make. I see a few options:
Make sure the API returns a String. However, this is probably extremely impactful as it is a breaking api change.
Revert the if statement in com.bunq.sdk.json.BigDecimalTypeAdapter so it becomes
Have Geolocation use Doubles instead of BigIntegers
My personal preference would go to option 2 since in my opinion it is a more resilient solution. I am willing to make the pull request myself. Just give me your decision.
The text was updated successfully, but these errors were encountered:
My apologies, I just noticed this was already fixed in a way quite similar to option 2.
I will build application using the develop branch for now and wait for the official release.
Steps to reproduce:
What should happen:
What happens:
Traceback
SDK version and environment
Response id
Extra info:
Currently
com.bunq.sdk.model.generated.object.Geolocation
has threeBigDecimal
fields. However, there seems to be a mismatch. If you take a look atcom.bunq.sdk.json.BigDecimalTypeAdapter
it reads aBigDecimal
from typeString
. Yet the api returns a value of type number.I did not make the pull request myself because I don't know which fix you'd like me to make. I see a few options:
String
. However, this is probably extremely impactful as it is a breaking api change.com.bunq.sdk.json.BigDecimalTypeAdapter
so it becomesGeolocation
useDouble
s instead ofBigInteger
sMy personal preference would go to option 2 since in my opinion it is a more resilient solution. I am willing to make the pull request myself. Just give me your decision.
The text was updated successfully, but these errors were encountered: