@navjodh_dhillon Again, this is true regardless of whether the parameters are merged.
The context for my request is this: the user requires that two different parameters are set to the same value, and the user is already successfully setting both parameters individually to the same value. The data-loss dilemma you’re raising (where the two parameters cannot hold the same value) cannot, by definition, occur within that context.
I can only think of two scenarios where the data-loss dilemma could actually occur:
- The user is confused about the purpose of a specific property, and is setting the wrong value.
- The developer chose the wrong type for a property
In either scenario, somebody is doing something wrong that needs to be corrected, and this is true regardless of whether the two parameters are merged.
So my contention is that merging parameters of different types is harmless and beneficial to working applications, and only presents data-loss issues to applications that are already broken.