We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unit_of_measurement gets capitalized so that "kW" becomes "KW", "mm" becomes "Mm", etc.
SI-prefixes such as "kilo" ("k") or "milli" ("m") should not be capitalized. (However, "giga" ("G"), "tera" ("T"), etc should).
I would suggest not modifying the unit_of_measurement at all, i.e. use what is specified by the platform or in configuration.yaml
Not sure if this is a frontend or backend issue, i.e. where the conversion takes place.
The text was updated successfully, but these errors were encountered:
It's a frontend thing. We capitalize the state + unit field using CSS.
On Tue, Jan 19, 2016, 23:59 Erik notifications@github.com wrote:
unit_of_measurement gets capitalized so that "kW" becomes "KW", "mm" becomes "Mm", etc. SI-prefixes such as "kilo" ("k") or "milli" ("m") should not be capitalized. (However, "giga" ("G"), "tera" ("T"), etc should). I would suggest not modifying the unit_of_measurement at all, i.e. use what is specified by the platform or in configuration.yaml Not sure if this is a frontend or backend issue, i.e. where the conversion takes place. — Reply to this email directly or view it on GitHub #938.
— Reply to this email directly or view it on GitHub #938.
Sorry, something went wrong.
No branches or pull requests
unit_of_measurement gets capitalized so that "kW" becomes "KW", "mm" becomes "Mm", etc.
SI-prefixes such as "kilo" ("k") or "milli" ("m") should not be capitalized.
(However, "giga" ("G"), "tera" ("T"), etc should).
I would suggest not modifying the unit_of_measurement at all, i.e. use what is specified by the platform or in configuration.yaml
Not sure if this is a frontend or backend issue, i.e. where the conversion takes place.
The text was updated successfully, but these errors were encountered: