You signed in with 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
{{ message }}
This repository has been archived by the owner on Mar 25, 2019. It is now read-only.
Should there be a value key, or should value (and sometimes children) simply be the sequential second key? Or perhaps both, with value overriding a sequential value?
If you can do whatever.value to set it that would make more sense then whatever[2]
If you are setting the value with a function then there is no point for an extra value field.
Priority override makes sense technically since the important one is the value as that would be changed but maybe it doesn't make sense in terms of clarity.
Well, it wouldn't be whatever[2], this is strictly for markup. See the
above examples.
On Jan 15, 2015 3:12 AM, "adrix89" notifications@github.com wrote:
If you can do whatever.value to set it that would make more sense then
whatever[2]
If you are setting the value with a function then there is no point for an
extra value field.
—
Reply to this email directly or view it on GitHub #15 (comment).
I've decided to go with the priority bit. You can use either element[2] or element.value to assign a value where element.value takes priority in the case that both are given.
Should there be a value key, or should value (and sometimes children) simply be the sequential second key? Or perhaps both, with value overriding a sequential value?
The text was updated successfully, but these errors were encountered: