Removing "or" assignment from exports, class and namespace declarations#512
Merged
Removing "or" assignment from exports, class and namespace declarations#512
Conversation
Perryvw
reviewed
Apr 7, 2019
Member
Perryvw
left a comment
Perryvw
left a comment
There was a problem hiding this comment.
Looks fine to me, I do still want to test this out (tomorrow).
Collaborator
Author
|
I've added 2 things to this PR:
|
Perryvw
approved these changes
Apr 10, 2019
Member
Perryvw
left a comment
Perryvw
left a comment
There was a problem hiding this comment.
Woops, forgot about this one. Tested it and works fine!
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
2 participants
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.
fixes #509
X = {}instead ofX = X or {}.@noClassOrhas been removed as it no longer does anythingexportkeyword