I’ve a string that’s a short record locator ID in document front matter (for example “F7BN” or “4E12”). I want to render these out per page, but while the first one works fine the second is being cast to a large number because it’s being read as exponential notation. The only way I’ve got so far of “fixing” this is quoting the ID in the front matter (e.g. id: "4E12" instead of id: 4E12) which is fine but feels inelegant.
The ID is set by a python script, and the python yaml parser just sees a string and dumps it without quotes. Not a problem per se, now I know this is the behaviour I can explicitly quote the string, but will need to check through a few hundred records for unquoted strings-that-happen-to-be-a-number. Was hoping I could guard against this on the Hugo side as well as fixing the python end.