Remove extra argument from WebAssemblyImportDependency constructor call site#6882
Merged
sokra merged 2 commits intowebpack:masterfrom Mar 29, 2018
Merged
Remove extra argument from WebAssemblyImportDependency constructor call site#6882sokra merged 2 commits intowebpack:masterfrom
sokra merged 2 commits intowebpack:masterfrom
Conversation
Contributor
|
Could you fix the formatting here please? You can run |
sokra
approved these changes
Mar 28, 2018
Contributor
Contributor
|
Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon. |
sokra
approved these changes
Mar 29, 2018
Member
|
Thanks |
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
4 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.
What kind of change does this PR introduce?
refactoring
Did you add tests for your changes?
no
If relevant, link to documentation update:
no
Summary
As part of #6862 I'm proposing fixes to issues TypeScript compiler have found
Does this PR introduce a breaking change?
no
Other information