Skip to content
This repository has been archived by the owner on Mar 25, 2021. It is now read-only.

Excuse edge cases in quotemark backtick (#4588) #4618

Merged
merged 1 commit into from
Mar 31, 2019
Merged

Excuse edge cases in quotemark backtick (#4588) #4618

merged 1 commit into from
Mar 31, 2019

Conversation

ericbf
Copy link
Contributor

@ericbf ericbf commented Mar 29, 2019

This commit fixes the cases where export statements, string literal type as generic type parameter, and string literals in object literal property assignments were incorrectly flagged. This also fixes a small lint error (specifying a type parameter same as default).

PR checklist

Overview of change:

This commit fixes the cases where export statements, string literal type as generic type parameter, and string literals in object literal property assignments were incorrectly flagged. This also fixes a small lint error (specifying a type parameter same as default).

Is there anything you'd like reviewers to focus on?

Make sure the tests capture all the use cases.

CHANGELOG.md entry:

[bugfix] quotemark: backtick option should no longer flag strings that require single/double quotes

This commit fixes the cases where export statements, string literal type as generic type parameter, and string literals in object literal property assignments were incorrectly flagged. This also fixes a small lint error (specifying a type parameter same as default).
Copy link
Contributor

@JoshuaKGoldberg JoshuaKGoldberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome, LGTM. Thanks @ericbf!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[quotemark: backtick] Incorrectly flags string literals in export line
2 participants