When the component is rendered by the view/in a digest cycle of angular, it triggers the function linked to changes. I don't believe this is a desired result of the digest cycle.
In our case we were sending requests to the backend because of it.
Would it be possible to fix this issue? Despite of this minor problem, our team really likes to work with this component.
When the component is rendered by the view/in a digest cycle of angular, it triggers the function linked to changes. I don't believe this is a desired result of the digest cycle. In our case we were sending requests to the backend because of it. Would it be possible to fix this issue? Despite of this minor problem, our team really likes to work with this component.
Have a great day!