↓ Skip to main content

Aurelia custom element async life cycle event

17 March 2016·1 min· ·

Blogger Archive Aurelia

Through the Haze - This article is part of a series.

Part : Python and SublimeText

Part : Aurelia View Engine Hook for importing enums, static variables, etc

Part : This Article

Part : JSON Web Token payloads

Part : Aurelia delegate vs trigger

Part : Aurelia change event Firefox woes

Part : We all make our mountains and we make them as tall as we need them

Part : Aurelia, Firefox and Input fields

Part : Dynamic input list in Aurelia

Part : Logging in Aurelia

Part : Enabling ES2016(ES7) Async functions in Aurelia

Part : Python SSH Tunnel Example

Part : Installation Notes for Flask App on Ubuntu 14.04 LTS using gUnicorn

Part : Insomnia due to back pain

Part : Acid Reflux, Camping, Hammocks and Holes

Part : String Similarity

Part : CAPEX, OPEX and Cloud?

Part : Fable of the porcupine

Part : Lab Notebook Digitization

Part : Google's Birthday Wishes

Part : Play to Work!

Part : Licensing terms: poison or fertilizer?

Part : Corporate havens of incompetence

Part : Training is the kiss of death

Part : AIM for Sales

Part : Citation Matching to Pubmed

Part : Microsourcing

I saw a really good conversation in the Aurelia/framework Github issue queue that I wanted to save for later. https://github.com/aurelia/framework/issues/367#issuecomment-198104416

From Rob Eisenberg:

We can’t provide this (async promise life-cycle events) across all components. It would be a disaster for performance and would no longer map in any way to web components.

If you don’t care about web components, you can use the new CompositionTransaction: http://aurelia.io/docs.html#/aurelia/templating/1.0.0-beta.1.1.2/doc/api/class/CompositionTransaction

Simply have that injected into your component constructor and then call enlist() this will return you a CompositionTransactionNotifier: http://aurelia.io/docs.html#/aurelia/templating/1.0.0-beta.1.1.2/doc/api/interface/CompositionTransactionNotifier

You can call done on that when your async operation is complete. The global composition will wait to attach until after you are done.

How do I wait for async data for an Aurelia custom element?

Through the Haze - This article is part of a series.

Part : Python and SublimeText

Part : Aurelia View Engine Hook for importing enums, static variables, etc

Part : This Article

Part : JSON Web Token payloads

Part : Aurelia delegate vs trigger

Part : Aurelia change event Firefox woes

Part : We all make our mountains and we make them as tall as we need them

Part : Aurelia, Firefox and Input fields

Part : Dynamic input list in Aurelia

Part : Logging in Aurelia

Part : Enabling ES2016(ES7) Async functions in Aurelia

Part : Python SSH Tunnel Example

Part : Installation Notes for Flask App on Ubuntu 14.04 LTS using gUnicorn

Part : Insomnia due to back pain

Part : Acid Reflux, Camping, Hammocks and Holes

Part : String Similarity

Part : CAPEX, OPEX and Cloud?

Part : Fable of the porcupine

Part : Lab Notebook Digitization

Part : Google's Birthday Wishes

Part : Play to Work!

Part : Licensing terms: poison or fertilizer?

Part : Corporate havens of incompetence

Part : Training is the kiss of death

Part : AIM for Sales

Part : Citation Matching to Pubmed

Part : Microsourcing

Related