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
This might be a bug in angular itself, but you might know the problem given we used the same setup as you did for tabs directives.
If we use two-way data binding on the pane directive's attributes (name: '=', title: '=') while it still works in the browser, the attributes are not picked up when run in the test environment using Angular Mock. Looking at a break in the link function, the scope is aware of its variables, but has null values for them. Using name: '@', title: '@' works fine in both environments.
Bug in Angular? Angular Mock? Something specific to this configuration?
Thanks!
The text was updated successfully, but these errors were encountered:
This might be a bug in angular itself, but you might know the problem given we used the same setup as you did for tabs directives.
If we use two-way data binding on the pane directive's attributes (name: '=', title: '=') while it still works in the browser, the attributes are not picked up when run in the test environment using Angular Mock. Looking at a break in the link function, the scope is aware of its variables, but has null values for them. Using name: '@', title: '@' works fine in both environments.
Bug in Angular? Angular Mock? Something specific to this configuration?
Thanks!
The text was updated successfully, but these errors were encountered: