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
When a promised module is rejected. If another (or the same) calling module requests the promised module, definejs request the module again or automatically reject the call based on the first on the first rejection (sorry for the confusion)?
The text was updated successfully, but these errors were encountered:
define([/*'dependency'*/],function(/*dependency*/){returnnewPromise(function(fulfill,reject){//fulfill when succeeded and pass the fulfillment value //otherwise your module definition gets rejected});});
And they still need more discussion and real world feedbacks for their rejection state. This issue will be open to discuss all the possible feedbacks around it. Feel free to bring up your views regarding the rejection state of promised modules and the way you would prefer to handle your modules definitions when they get rejected.
When a promised module is rejected. If another (or the same) calling module requests the promised module, definejs request the module again or automatically reject the call based on the first on the first rejection (sorry for the confusion)?
The text was updated successfully, but these errors were encountered: