You signed in with
8000
another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we did this I think we shoud also create a removeKey. But what should we do with the data that has already been transposed? We may have to add options to it like removeKey('color, { delete: true }).
We also have a similar problem with addKey. The way you've described it is that if someone added a key after adding all the data then that key would have a transpoition of all exisiting data already. Which means that we would either have to transpose all keys as we go (which we do on redesign unless you specify options.keys) or transpose the entirety of original again, which would be costly.
I don't think we should do this.
If someone specifies options.key then they must stick to that and, if they don't, then all keys are transposed anyway in redesign.
Activity
j-m commentedon May 12, 2019
If we did this I think we shoud also create a
removeKey. But what should we do with the data that has already been transposed? We may have to add options to it likeremoveKey('color, { delete: true }).We also have a similar problem with
addKey. The way you've described it is that if someone added a key after adding all the data then that key would have a transpoition of all exisiting data already. Which means that we would either have to transpose all keys as we go (which we do onredesignunless you specifyoptions.keys) or transpose the entirety oforiginalagain, which would be costly.I don't think we should do this.
If someone specifies
options.keythen they must stick to that and, if they don't, then all keys are transposed anyway inredesign.