It was brought to our attention that the integer
value type in our metafields API wasn't working the way you'd expect and required weird hacks in liquid such as {{ metafield.value | plus: 0}}
to coerce the values back into integers. This was anything but desirable and we wanted to correct this discrepancy. There were some side-effects that came out of this which were accidental.
This change fixes the way the Shopify Metafield API behaves. According to the documentation two value_types
are supported, string
and integer
though the integer
value wasn't being respected and was simply just a string
.
With the changes that have been deployed; if your field was an set to an integer
value_type
it will be properly coereced into the data-type you are expecting. Though if you were using the field incorrectly such as storing `"some string dat