Let's say the user sets expectedLoadTime to 4000. Then they decide they don't want this property in the config and then clear the input field.
This results in expectedLoadTime being set to '' i.e. the empty string. This would be pretty disrespectful and a RAMP instance initialized with such a property would likely have errors.
This happens because of how Vue's v-model works under the hood. People have already attempted to grouse but to no avail.
This is a pretty significant problem because it is currently affecting all numeric properties in the config.
One solution (thank you @milespetrov for the suggestion) is to code a custom directive and use the logic for all numeric fields.
Let's say the user sets
expectedLoadTimeto 4000. Then they decide they don't want this property in the config and then clear the input field.This results in
expectedLoadTimebeing set to''i.e. the empty string. This would be pretty disrespectful and a RAMP instance initialized with such a property would likely have errors.This happens because of how Vue's
v-modelworks under the hood. People have already attempted to grouse but to no avail.This is a pretty significant problem because it is currently affecting all numeric properties in the config. One solution (thank you @milespetrov for the suggestion) is to code a custom directive and use the logic for all numeric fields.