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
It would be nice to have a masseuse formatter. There are times when rivets formatters are not adequate. The different between a masseuse formatter and a computed property is that the value is represented differently when being read vs being published.
In the following example, the value would be lowercase when being read (in the UI) and uppercase when being published (sent to server)
from a masseuse view model:
inputValue : newmasseuse.ProxyProperty('transaction',this.model),//this could be a proxy or a computeddisplayedValue : newmasseuse.Formatter(function(inputValue){returnotherValue.toLowerCase();},function(inputValue){returnotherValue.toUpperCase();});
OR,
The current proxy properties can accept optional 3rd and 4th parameters. These would be a read and publish funciton.
It would be nice to have a masseuse formatter. There are times when rivets formatters are not adequate. The different between a masseuse formatter and a computed property is that the value is represented differently when being read vs being published.
the interface would look something like this:
In the following example, the value would be lowercase when being read (in the UI) and uppercase when being published (sent to server)
from a masseuse view model:
OR,
The current proxy properties can accept optional 3rd and 4th parameters. These would be a read and publish funciton.
OR,
Make a computed from a proxy:
The text was updated successfully, but these errors were encountered: