Currently, the bounty_amount object on H1 is returned as a float, while previously it was a int. As such, the previous way we used to parse these numbers was insufficient, and led to a bug of the amount being off by a factor of 100:
bounty_amount: 500.00
Expected: 500
Actual: 50000
This PR makes the gsub filters less stringent to allow a decimal point to pass through, and casts to float instead of to int.
Apparently, these are just methods defined in Kernel that have nothing to do with the underlying objects they create, they just happen to share a name.
Currently, the bounty_amount object on H1 is returned as a float, while previously it was a int. As such, the previous way we used to parse these numbers was insufficient, and led to a bug of the amount being off by a factor of 100:
This PR makes the gsub filters less stringent to allow a decimal point to pass through, and casts to float instead of to int.