Fixed incorrect promise resolving in script-writer#24
Open
theUNnicked wants to merge 1 commit intoDAB0mB:masterfrom
Open
Fixed incorrect promise resolving in script-writer#24theUNnicked wants to merge 1 commit intoDAB0mB:masterfrom
theUNnicked wants to merge 1 commit intoDAB0mB:masterfrom
Conversation
…oading next script
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR fixes the issue with scripts loader. I have observed that some scripts return
<script type="text/javascript">undefined</script>instead of expected script value.This happens because of incorrect promise resolution.
Currently resolving the promise results in returning script onLoad event instead of next variable.
The issue lies with the fact that the return value from the promise executor is ignored. The variable should be passed to the resolve function instead.