I’m confused on the best practice method to write providers for async operations, and I need some help. Besides thinking of them as ways to persist data across pages, I consider them as ‘gateways’ to various external entities, such as firebase or http… therefore, I try to put all code that communic…

1 is not dry and silly for that matter. U find this a lot on this forum but is not because of best practice (although I have seen some cases doing a new Promise to convert a callback method to Promise) 2 is what I do and recommend 3 is basically transforming your app into a universal service bus w…

I basically agree with @Tommertom if these are the only options we are given, but I would suggest a #4 that he hinted at: actually do convert the promise to an observable. The primary reason for this is that promises can only be one-night stands; observables can be lasting relationships. Consider th…

Thanks for your input. I’m definitely trying to wrap my head around using providers instead of coding all interactions in the page itself. Managing the asynchronous aspects seems to be the most difficult part between those worlds.

[image] wterrill: firebase-auth, firebase-database, firebase-storage, etc I’m not sure if this is a naming convention thing or an actual design structure thing, but I would do this differently. I design consumers first and providers second, and consumers (generally pages) don’t care and shoul…

I hadn’t thought of the emitters being makeshift observables…You’re right, observables would definitely be preferable.

can you speak a little bit more about that? what design decisions pushed you in that direction? The reason I had designed my providers with the idea of, “ Gateway to where the data came from” was based on the notion that I could swap out functionality with a different web service if needed. I.e. …

[image] wterrill: maybe that what you’re saying? That the naming of the provider should be independent of firebase, sql, mongo…As long as it’s providing the same data? Right, therefore it should not have the “where” in its name. Specifically, having both something named “storage” and somethin…

Agree to option 4 as the ideal solution. This example I like a lot as it shows using the observable pattern for settings of a global style https://devdactic.com/dynamic-theming-ionic/

Outstanding. Thanks for the explantation!

Two quick things: Your option (1) has an “official” name: the Explicit Promise Construction Antipattern. As you might guess, it’s considered bad practice. In my own code, the only time I’ve had to use “return new Promise” was when I was promisifying something that was not originally a Promise. …

How to write async operations in providers

Ionic Framework ionic-v3

rapropos March 25, 2018, 7:43pm 13

Anything Ionic’s Events can do can be done better using Observables.

Topic		Replies	Views
Provider/server: Provide the data or contain the data? ionic-v3	10	3695	August 14, 2017
Keep data in service, or in Pages? ionic-v3	24	2639	December 1, 2017
Synchronization between different components ionic-v3	10	2891	May 24, 2017
Sharing data between pages in app ionic-v3	1	1215	October 26, 2017
Best practice advice - Observable, promises and ordering within a provider ionic-v3	6	13597	September 28, 2017

How to write async operations in providers

Related topics