[FIX] Require logic is faulty for compiled apps #40
Conversation
This file contains 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
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.
The logic used to
requiremodules after the app is compiled was wrong, considering only the result from evaluating the last line from the required script.We needed to handle this case due to backward compatibility since the main class file might export a class with an unknown name, which was supported in the early versions of the Apps-Engine.
This PR fixes the problem by returning the previous result ONLY IF we find that the required file exports ONLY ONE property, which is what happens in the case of the main class file; otherwise, we return the full
exportsobject.