Why are Height, Width, Length and Weight integer instead of type decimal? #3794
Replies: 6 comments 1 reply
-
|
I agree with this, this should absolutely be allowed. It seem very arbitrary to force upon integers here. That being said, I have found some workarounds besides using metadata for sizes. For example with the metric system, it would be enough to set "mm" instead of "cm". For weight, instead of "kg", we would use "g". If you want to display these in "kg" or "cm", you would then handle that logic in the frontend with conversion. I assume you can do the same with the imperial system of measurement. |
Beta Was this translation helpful? Give feedback.
-
|
is there any updates on this? the fact dimensions are in integer are kinda a big deal for certain products |
Beta Was this translation helpful? Give feedback.
-
|
Theoretically, could we just migrate the underlying postgres table column to |
Beta Was this translation helpful? Give feedback.
-
|
I just migrated over 2000 products and most of the weights are wrong because of the conversion to int. |
Beta Was this translation helpful? Give feedback.
-
|
Any update about this? It doesn't make sense to be int. Weight is a continuous quantity. An object can have any mass value, including fractions. |
Beta Was this translation helpful? Give feedback.
-
|
Any update about this? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Why are the fields of Height, Width, Length and Weight integer instead of decimal? Consumers and even 3rd party systems need to know the exact measurements and weights of products. Could you please explain?
Beta Was this translation helpful? Give feedback.
All reactions