This goal:
https://www.beeminder.com/narthur/tr-cards
Has this setting:
So why does the API return integery: false
for this goal?
Also, would be nice to be able to get the specific display precision selected via the API.
This goal:
https://www.beeminder.com/narthur/tr-cards
Has this setting:
So why does the API return integery: false
for this goal?
Also, would be nice to be able to get the specific display precision selected via the API.
Because it’s not flagged as integery, it just has a display quantum of 1.
Besides which, integery is deprecated and shanaqui once expressed a suspicion that it’d behave badly alongside setting the display precision.
Hmm, ok. Any chance beeminder could run a migration from the one setting to the other and then just define integery in the api as precision == "1"
or are there differences between how the two settings work that I don’t understand?