[Fix] order: ignore requires in template literal#1940
Merged
Conversation
Member
|
Thanks! It seems like a more general fix is in order; the only requires that this rule should warn on are module-level requires, whether in a template literal or not. |
Contributor
Author
|
It sounds great to only warn on module-level requires! There are two cases I am unsure about, they are not strictly module-level requires: const bar = require('foo').barconst foo = require('foo')()I handled both of them anyway, if just for backward compatibility. |
Member
|
Those are module-level requires, even tho they're immediately destructured. Thanks for handling them! |
|
@golopot Thank you for fixing! |
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
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 #1936.