Closed acrose99 closed 2 years ago
I'm a little suspicious that this might be due to measurement settings set in the MFP UI, and that we might instead need to either update the docs to make this ambiguous, or somehow look up the unit used in the user's settings. I unfortunately don't use this particular feature, so I can't say for sure offhand -- do any of you all who use this have any insight?
I'm a little suspicious that this might be due to measurement settings set in the MFP UI, and that we might instead need to either update the docs to make this ambiguous, or somehow look up the unit used in the user's settings. I unfortunately don't use this particular feature, so I can't say for sure offhand -- do any of you all who use this have any insight?
It seems to always come back as milliliters regardless of user unit preference. Either way, we are reading the "milliliters" node of the json response, so it's probably safe to assume that this will be in milliliters.
[...] Either way, we are reading the "milliliters" node of the json response, so it's probably safe to assume that this will be in milliliters.
That... is an excellent point! I'm convinced.
On the readMe documentation for getting your cups of water it says
However, as it stands, _get_water in the client returns the millimeters of recorded, not the cups.
Therefore I would either update the readMe or change the client code like I've done in this pull request!
New readMe:
Obviously the readMe change is easy, but let me know if my code isn't good enough and I can try again. Thanks!!