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 Jan 14, 2020. It is now read-only.
Both locationsService and productsService provide a callOnReplicationComplete function. While that function was created to be used by other angular-nav-data services (lgasService, statesService, zonesService and productsListService) and it works fine for those, since it's publicly available it could also be used by components within the app including angular-nav-data as a dependency. Since components are created and destroyed all the time, in order to have the right component registered to an event without going over the limit of the EventEmitter is to register to the event $onInit and unregister $onDestroy, for that a function for unregistering callbacks is required.
The text was updated successfully, but these errors were encountered:
patriciagarcia
changed the title
allow to unregistered registered "on complete" callbacks
allow to unregister registered "on complete" callbacks
Aug 9, 2016
Both
locationsService
andproductsService
provide acallOnReplicationComplete
function. While that function was created to be used by otherangular-nav-data
services (lgasService
,statesService
,zonesService
andproductsListService
) and it works fine for those, since it's publicly available it could also be used by components within the app includingangular-nav-data
as a dependency. Since components are created and destroyed all the time, in order to have the right component registered to an event without going over the limit of theEventEmitter
is to register to the event$onInit
and unregister$onDestroy
, for that a function for unregistering callbacks is required.The text was updated successfully, but these errors were encountered: