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
Browser:
all | Chrome XX | Firefox XX | Edge XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView
Language:
ESNext
Current behavior:
propertyChanged method is never called in a unit test. Here is a sample custom element view model
@EisenbergEffect thanks for the info. I will comment on the other referenced issue as that is the reason which made us try to test our custom elements in this way
I'm submitting a bug report
1.0.0-beta.3.0.1
Please tell us about your environment:
Operating System:
OSX
Node Version:
7.9.0
4.2.0
webpack 2.6.1
Browser:
all | Chrome XX | Firefox XX | Edge XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView
Language:
ESNext
Current behavior:
propertyChanged method is never called in a unit test. Here is a sample custom element view model
Here is my sample test case:
After I set the name of the view model, the nameChanged method is not called and test fails.
Expected/desired behavior:
nameChanged
method should be called when the bindable propertyname
is changed.The text was updated successfully, but these errors were encountered: