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
Currently there's no way to tell if an invalid property is supplied, so for instance; if you misspelled modifer: 'someVal' there's no indicator that the property won't be acted upon. Since we want to allow custom properties my suggestion is to "throw" a warning if the key in a definition is not recognized, then create a obey.customProps(<array|string>) that allows for centrally declaring custom props to prevent the warning.
The text was updated successfully, but these errors were encountered:
ksafranski
changed the title
Warnings for non-reigstered properties
Warnings for non-native properties
Mar 17, 2016
Currently there's no way to tell if an invalid property is supplied, so for instance; if you misspelled
modifer: 'someVal'
there's no indicator that the property won't be acted upon. Since we want to allow custom properties my suggestion is to "throw" a warning if the key in a definition is not recognized, then create aobey.customProps(<array|string>)
that allows for centrally declaring custom props to prevent the warning.The text was updated successfully, but these errors were encountered: