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
In the first invocation of the listener , newParams is equal to oldParams - this is because of angular limitation :
"After a watcher is registered with the scope, the listener fn is called asynchronously > (via $evalAsync) to initialize the watcher. In rare cases, this is undesirable because the listener is called when the result of watchExpression didn't change. To detect this scenario within the listener fn, you can compare the newVal and oldVal. If these two values are identical (===) then the listener was called due to initialization."
This has the side effect that the first call to getData will use the default getData and not the one provided by the user, because at this stage the settings weren't yet processed.
The text was updated successfully, but these errors were encountered:
When watching the table parameters for changes:
In the first invocation of the listener , newParams is equal to oldParams - this is because of angular limitation :
This has the side effect that the first call to getData will use the default getData and not the one provided by the user, because at this stage the settings weren't yet processed.
The text was updated successfully, but these errors were encountered: