Bug / unexpected behavior with leading zeros - number / string widget

Big bug on my side.

I wanna have a color picker / HEX sort of thing. Right now it’s just numbers, but if I have a HEX code that starts with zeros, the end result is wrong.

008000 generates 8000. Help.

https://github.com/cstate/cstate/issues/83

If I try and enter "008000", there’s double quotes which confuse Hugo. In turn, the color HEX becomes #ZgotmplZ.

Is there something I can do to prevent the assumption that I don’t need the first two zeros?

[erquhart]

The CMS isn’t removing the zeros. I would expect the double quotes to be from quotes being manually added to the string input.

_{Sent with GitHawk}

[erquhart]

The source shows zeroes, but any yaml -> json converters I can find drop the leading zeroes if quotes are not present. That said, I think I found my final recommendation: include the leading hash. A hex code is supposed to begin with a hash to be valid, and doing so ensures leading zeroes never drop. I’d recommend storing hashes in your raw values.