JavaScript From my directive, how can I manually trigger a digest cycle on my parent scope?

I have a directive that I would like to force render when a change is made to an underlying model programmatically. $scope.$apply is idiomatic. But I am unable to get the directive to render without clicking repeatedly on the UI (which presumably manually forces the digest).

Can someone help me identify how to manually trigger the digest?

Even this.scope.$root.$apply() has no effect.

Grabbing hold of a parent DOM node and getting the associated scope, then calling $apply on that from the console, does work however.

When using this DOM node approach in the code it does not work however. Why might this be?

Answer:1

Two things to note:

Scopes inherit from each other prototypically and form a tree. Scopes have a reference to $parent which can be used to traverse.
A digest cycle is something that happens on a scope object. Ie. $scope.$digest(). This runs a digest on the scope, and then recursively does the same for all of the child scopes. $scope.$apply() is like doing $rootScope.$digest(). Since it starts at the root, it calls a digest on every other scope. So $apply might be excessive.

To answer your question, scope.$parent.$digest() will trigger a digest on scope's parent.

But it seems that the triggering of the digest isn't actually your problem. $apply will trigger digests on all scopes, so if that isn't working for you, I don't think your problem is simply that you need a digest to be triggered.

Perhaps you don't need the whole directive to re-render, but just need a part of it to update? If so, consider data binding to some shared service like this.

HTML

<div ng-app='app'>
  <one></one>
  <two></two>
</div>

angular
  .module('app', [])
  .directive('one', function() {
    return {
      restrict: 'E',
      scope: {},
      template: "<input ng-model='shared.val'> {{ shared.val }}",
      controller: function($scope, Shared) {
        $scope.shared = Shared;
      }
    };
  })
  .directive('two', function() {
    return {
      restrict: 'E',
      scope: {},
      template: '<p> {{ shared.val }}</p>',
      controller: function($scope, Shared) {
        $scope.shared = Shared;
      }
    };
  })
  .factory('Shared', function() {
    return {
      val: ''
    };
  });

Answer:2

On button click put all elements src to array

I have many divs with id="imgLinks" <div><img id="imgLinks" u=image src="../../../../images/1.jpg" /></div> <div><img id="imgLinks" u=image src="../../../../images/3.jpg"...

document.getElementById as jQuery selector

I saw this pattern being used in some code... currency = $(document.getElementById('currency')); Which is expect is functionally equivalent to... currency = $('#currency'); I am guessing the idea ...

document.getelementbyid jquery
document.getelementbyid jquery alternative
document.getelementbyid jquery equivalent
document.getelementbyid jquery selector
document.getelementbyid jquery value
document.getelementbyid jquery example
document.getelementbyid vs jquery
document.getelementbyid vs jquery performance
document.getelementbyid innerhtml jquery
document.getelementbyid vs jquery selector
document.getelementbyid in jquery w3schools
document.getelementbyid using jquery
document.getelementbyid.src jquery
document.getelementbyid(id) jquery
document.getelementbyid or jquery faster
parent.document.getelementbyid jquery
document.getelementbyid vs jquery id selector
javascript document.getelementbyid jquery
document getelementbyid disabled jquery
document.getelementbyid.checked jquery

Getting selected node path or depth tree view in angular JS or depth

I want to get the selected node path from root in tree view by using AngularJS. I have seen this link. It is used to get only selected node like subUser2. But i want to display selected Node path or ...

NodeJS best practices with Promises

I am developing a new library above amqp.node (amqplib), basically we dont need all the RabbitMQ functionality. So, I am creating a simple library that facilitates the usage specifically for our ...

nodejs best practices github
node js best practices 2019
node js best practices file structure
node js best practices 2020
node js best practices medium
node js best practices folder structure
node js best practices for production
node js best practices require
node js best practices
node js best practices 2018
node js module best practices
node js best practices tutorial
mongoose node js best practices
node js best practices conventions
nodejs logging best practices
nodejs docker best practices
nodejs express best practices
nodejs api best practices
nodejs dockerfile best practices
nodejs rabbitmq best practices