We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
One of possible proposal is to use ~ or ! to declare such callbacks:
~
!
bemDom.decl*('block', { onSetMod : { 'm1' : { 'v1' : function() { }, '~v1' : function() { // v1 -> * // code }, '!v1' : function() { // v2 -> v3 // code } } } });
In the example above ~v1 is an aliases for
~v1
onSetMod : { 'm1' : { '*' : function(modName, modVal, prevModVal) { if(prevModVal === 'v1') { // code } } } }
!v1 is an aliases for
!v1
onSetMod : { 'm1' : { '*' : function(modName, modVal) { if(modVal !== 'v1') { // code } } } }
The text was updated successfully, but these errors were encountered:
cc @veged
Sorry, something went wrong.
i-bem: Add ability to specify onSetMod callback called when specific …
509d460
…value changed to another (close #1072)
Merge pull request #1089 from /issues/1072@v3
7de2df9
i-bem: Add ability to specify onSetMod callback called when specific value changed to another
veged
No branches or pull requests
One of possible proposal is to use
~
or!
to declare such callbacks:In the example above
~v1
is an aliases for!v1
is an aliases forThe text was updated successfully, but these errors were encountered: