Where is that fix implemented Trystan?
I raised an issue on emoncms (#977) about some formatting of a api reply, while looking into that I learned about the php json.encode() defaults and suggested those defaults get over-ruled and the “emoncms defaults” get set in a wrapper function for encoding JSON.
The numerical values being returned as strings has come up before as you know (#273 and #540), I’m guessing that maybe using proper float JSON settings that might also handle nulls, infs and nans without manually handling the stings as has been the case in the past, but that is just a guess 
As it happens I was using feedvalue widgets the other day and found it frustrating that I could not set both a pre-fix and post-fix (unit) eg
Temp1 <val> °C
I had to chose between putting the single “unit” field before or after the value. That selection (before or after) uses a field itself. IMO it would be better to have a leading text and trailing text, still only 2 fields but vastly more flexible.
I currently have to use
<val> °C (Temp1)
which I really don’t like. I could have a seperate second text box, but I find myself dragging these around alot and having to try and keep the textbox and feedvalue grouped and aligned is a pain.
Annnnd… (since you ask)
It would be real nice if the widget settings could be carried forward when creating a batch of new feedvalues. I recently set up 40 feed values on one page all the same, but the font, weight and size all had to be changed individually, it would be nice if I could have set up one and then the next “new feed value” had the settings applied from the last. it only needs to last the edit session, I think it would get a bit messy for users to be able to save their own widget settings. Could this be possible by changing the scope of the widget variables?