This repository was archived by the owner on Apr 12, 2024. It is now read-only.
'unshift' argument for provider's loader#9364
Closed
mykolaharmash wants to merge 1 commit into
Closed
Conversation
Member
Author
|
I'm not sure, but might be that many users will stay on 1.2.x for a while after 1.3 release (maybe IE8 compatibility reason, etc.). Will be useful to fix this to avoid bad practices like described in #7147. Would be cool to implement separate configQueue just like in 1.3. |
Contributor
|
We cannot backport the fix as this would be a breaking change, sorry. Please update to 1.3.x... |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Providers are used in config blocks, but in case when config block invokes before provider, there is no-provider error. This situation may appear when module and config block declared in one file, and provider - in another. Eg.
module.js
foo-provider.js
Code from module.js always runs first and causes an error. There is fiddle
What do you think?