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
{{ message }}
This repository has been archived by the owner on May 22, 2023. It is now read-only.
The angular adapter needs to hook into promise in order to kick off a digest cycle when an eventBus.publish(...) or an eventBus.publishAndGatherReplies(...) completes.
The current workaround mechanism essentially breaks the native promise by replacing it with $q, so we need to fix it.
Alternatives:
patch window.Promise.prototype.then to have it trigger a digest cycle when the completion/rejection callback is invoked. This is a complete solution, but may have unintended side effects, e.g. performance problems.
decorate axEventBus for AngularJS widgets so that publish/publishAndGatherReplies returns a decorated promise, that again triggers a digest cycle. We need to check if this covers all our bases.
The text was updated successfully, but these errors were encountered:
Note: it is fine if the solution does not make Promise.resolve() magically trigger digest-cycles when used from AngularJS widgets! We just have to make sure that our libraries (laxar, laxar-patterns) function seamlessly.
The angular adapter needs to hook into promise in order to kick off a digest cycle when an
eventBus.publish(...)
or aneventBus.publishAndGatherReplies(...)
completes.The current workaround mechanism essentially breaks the native promise by replacing it with
$q
, so we need to fix it.Alternatives:
patch
window.Promise.prototype.then
to have it trigger a digest cycle when the completion/rejection callback is invoked. This is a complete solution, but may have unintended side effects, e.g. performance problems.decorate
axEventBus
for AngularJS widgets so that publish/publishAndGatherReplies returns a decorated promise, that again triggers a digest cycle. We need to check if this covers all our bases.The text was updated successfully, but these errors were encountered: