Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: enable prefer-template #9544

Merged
merged 10 commits into from
Aug 14, 2024

Conversation

abrahamguo
Copy link
Contributor

@abrahamguo abrahamguo commented Jul 11, 2024

PR Checklist

Overview

Enable prefer-template (docs). 100% autofixable.

@typescript-eslint
Copy link
Contributor

Thanks for the PR, @abrahamguo!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!


🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint.

Copy link

netlify bot commented Jul 11, 2024

Deploy Preview for typescript-eslint ready!

Name Link
🔨 Latest commit 43e7d8c
🔍 Latest deploy log https://app.netlify.com/sites/typescript-eslint/deploys/66a69aa996568400081179f6
😎 Deploy Preview https://deploy-preview-9544--typescript-eslint.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 98 (🔴 down 1 from production)
Accessibility: 100 (no change from production)
Best Practices: 92 (no change from production)
SEO: 90 (no change from production)
PWA: 80 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify site configuration.

`import type * as ${safeName} from '${from}';\n` +
text.replace(regex, safeName)
);
return `import type * as ${safeName} from '${from}';\n${text.replace(
Copy link
Member

Choose a reason for hiding this comment

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

Make \n a literal character

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is just a curiosity question — do you feel it's a case-by case decision on whether to use an explicit \n vs a literal newline?

I was just curious because there are hundreds of places throughout our codebases that use explicit \ns, so I was wondering if you were in favor of any consistent pattern, or if it just depends?

Copy link

codecov bot commented Jul 11, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.45%. Comparing base (6b92aa5) to head (43e7d8c).
Report is 186 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #9544      +/-   ##
==========================================
- Coverage   88.45%   88.45%   -0.01%     
==========================================
  Files         422      422              
  Lines       14695    14694       -1     
  Branches     4298     4298              
==========================================
- Hits        12998    12997       -1     
  Misses       1372     1372              
  Partials      325      325              
Flag Coverage Δ
unittest 88.45% <100.00%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
...lugin-internal/src/rules/plugin-test-formatting.ts 79.19% <100.00%> (ø)
...lugin/src/rules/consistent-generic-constructors.ts 90.24% <ø> (ø)
...es/eslint-plugin/src/rules/no-floating-promises.ts 100.00% <ø> (ø)
...es/eslint-plugin/src/rules/no-unsafe-assignment.ts 94.26% <ø> (ø)
...es/eslint-plugin/src/rules/prefer-function-type.ts 97.10% <100.00%> (-0.05%) ⬇️
.../rules/prefer-optional-chain-utils/analyzeChain.ts 100.00% <ø> (ø)
packages/eslint-plugin/src/rules/unbound-method.ts 95.29% <ø> (ø)
...rc/rules/use-unknown-in-catch-callback-variable.ts 100.00% <ø> (ø)

Josh-Cena
Josh-Cena previously approved these changes Jul 23, 2024
Copy link
Member

@Josh-Cena Josh-Cena left a comment

Choose a reason for hiding this comment

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

Leaving my +1

packages/eslint-plugin/tests/docs.test.ts Outdated Show resolved Hide resolved
@Josh-Cena
Copy link
Member

I know some of y'all have strong (and different) opinions about code, and this seems like a less straightforward one, so let's get more opinions.

@kirkwaiblinger
Copy link
Member

As noted in discussion, I'm not a big fan of this approach to solving the reports by this rule. I think we should reach for an aliased variable for cases with anything more than a truly trivial expression in the interpolation.

However, I'll leave an approval to signal there's nothing problematically merge-blocking and that you should feel free to proceed without satisfying my stylistic preferences 🙂

Copy link
Member

@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.

Yeah I'm not super picky here 😄, let's just merge and see how it goes. Thanks!

@JoshuaKGoldberg JoshuaKGoldberg merged commit 243fb5f into typescript-eslint:main Aug 14, 2024
62 checks passed
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 25, 2024
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.

4 participants