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

feat(eslint-plugin): [explicit-function-return-type] add allowIIFEs option #6237

Merged
merged 16 commits into from Feb 12, 2023

Conversation

yeonjuan
Copy link
Contributor

PR Checklist

Overview

@typescript-eslint
Copy link
Contributor

Thanks for the PR, @yeonjuan!

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.

@nx-cloud
Copy link

nx-cloud bot commented Dec 17, 2022

☁️ Nx Cloud Report

CI is running/has finished running commands for commit f18a367. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch


✅ Successfully ran 47 targets

Sent with 💌 from NxCloud.

@netlify
Copy link

netlify bot commented Dec 17, 2022

Deploy Preview for typescript-eslint ready!

Name Link
🔨 Latest commit f18a367
🔍 Latest deploy log https://app.netlify.com/sites/typescript-eslint/deploys/63e924cb75acbc000848b2bb
😎 Deploy Preview https://deploy-preview-6237--typescript-eslint.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

@codecov
Copy link

codecov bot commented Dec 17, 2022

Codecov Report

Merging #6237 (1c702dc) into main (766ab1d) will increase coverage by 0.00%.
The diff coverage is 100.00%.

❗ Current head 1c702dc differs from pull request most recent head f18a367. Consider uploading reports for the commit f18a367 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #6237   +/-   ##
=======================================
  Coverage   90.61%   90.61%           
=======================================
  Files         372      372           
  Lines       12709    12712    +3     
  Branches     3739     3740    +1     
=======================================
+ Hits        11516    11519    +3     
  Misses        853      853           
  Partials      340      340           
Flag Coverage Δ
unittest 90.61% <100.00%> (+<0.01%) ⬆️

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

Impacted Files Coverage Δ
...-plugin/src/rules/explicit-function-return-type.ts 97.95% <100.00%> (+0.13%) ⬆️

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.

Looks lovely to start! Just requesting a bit more test coverage please. 🙌

endColumn: 22,
},
],
},
Copy link
Member

Choose a reason for hiding this comment

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

Let's add a bit more test coverage:

  • IIFEs with return types
  • Multiple levels of IIFEs (e.g. (() => () => {})()())
  • Arguments & parameters

@JoshuaKGoldberg JoshuaKGoldberg added the awaiting response Issues waiting for a reply from the OP or another party label Dec 17, 2022
{
filename: 'test.ts',
code: `
let foo = (() => () => {})()();
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@JoshuaKGoldberg
How should we handle multiple levels of IIFEs? For now, it allows only if the function is called directly.

const foo = (() => () => "foo")()(); // error

const bar = (() => (() => "foo")())(); // pass

Should both cases be passed when the allowIIFEs option is true?

Copy link
Member

Choose a reason for hiding this comment

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

@yeonjuan The first one IMO is not an "IIFE" by definition—(() => () => "foo")() is an expression that happens to evaluate to a function, not a function expression itself. It's fine if we don't handle it.

Copy link
Member

Choose a reason for hiding this comment

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

I would agree with that assessment.
The inner function is not an IIFE, just the outer function.

@bradzacher bradzacher removed the awaiting response Issues waiting for a reply from the OP or another party label Jan 19, 2023
@bradzacher bradzacher added the enhancement: plugin rule option New rule option for an existing eslint-plugin rule label Jan 30, 2023
@JoshuaKGoldberg JoshuaKGoldberg added the awaiting response Issues waiting for a reply from the OP or another party label Feb 5, 2023
@JoshuaKGoldberg
Copy link
Member

👋 ping @yeonjuan, is this still something you have time for? And if so, do you have all the answers you need?

@yeonjuan
Copy link
Contributor Author

yeonjuan commented Feb 5, 2023

@JoshuaKGoldberg Sorry for the late, I missed some comment notifications. I'll work on this in this week!

# Conflicts:
#	packages/eslint-plugin/src/rules/explicit-function-return-type.ts
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.

Super thanks @yeonjuan! 🚀

This is looking great - I'll do the one probably-doesn't-matter touchup and merge.

@JoshuaKGoldberg JoshuaKGoldberg merged commit a1b3f7b into typescript-eslint:main Feb 12, 2023
crapStone pushed a commit to Calciumdibromid/CaBr2 that referenced this pull request Feb 14, 2023
This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint) | devDependencies | minor | [`5.51.0` -> `5.52.0`](https://renovatebot.com/diffs/npm/@typescript-eslint%2feslint-plugin/5.51.0/5.52.0) |
| [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint) | devDependencies | minor | [`5.51.0` -> `5.52.0`](https://renovatebot.com/diffs/npm/@typescript-eslint%2fparser/5.51.0/5.52.0) |

---

### Release Notes

<details>
<summary>typescript-eslint/typescript-eslint (@&#8203;typescript-eslint/eslint-plugin)</summary>

### [`v5.52.0`](https://github.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#&#8203;5520-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5510v5520-2023-02-13)

[Compare Source](typescript-eslint/typescript-eslint@v5.51.0...v5.52.0)

##### Bug Fixes

-   **eslint-plugin:** \[no-import-type-side-effects] correctly ignore zero-specifier imports ([#&#8203;6444](typescript-eslint/typescript-eslint#6444)) ([d5a6688](typescript-eslint/typescript-eslint@d5a6688))
-   **eslint-plugin:** \[no-unnecessary-condition] account for optional chaining on potentially void values ([#&#8203;6432](typescript-eslint/typescript-eslint#6432)) ([e1d9c67](typescript-eslint/typescript-eslint@e1d9c67)), closes [#&#8203;5255](typescript-eslint/typescript-eslint#5255)
-   **eslint-plugin:** \[no-unnecessary-condition] fix false positive when checking indexed access types ([#&#8203;6452](typescript-eslint/typescript-eslint#6452)) ([d569924](typescript-eslint/typescript-eslint@d569924))
-   **eslint-plugin:** fix key-spacing when type starts on next line ([#&#8203;6412](typescript-eslint/typescript-eslint#6412)) ([3eb2eed](typescript-eslint/typescript-eslint@3eb2eed))

##### Features

-   **eslint-plugin:** \[block-spacing] extending base rule for TS related blocks ([#&#8203;6195](typescript-eslint/typescript-eslint#6195)) ([b2db3f5](typescript-eslint/typescript-eslint@b2db3f5))
-   **eslint-plugin:** \[explicit-function-return-type] add allowFunctionsWithoutTypeParameters option ([#&#8203;6105](typescript-eslint/typescript-eslint#6105)) ([113640e](typescript-eslint/typescript-eslint@113640e))
-   **eslint-plugin:** \[explicit-function-return-type] add allowIIFEs option ([#&#8203;6237](typescript-eslint/typescript-eslint#6237)) ([a1b3f7b](typescript-eslint/typescript-eslint@a1b3f7b))

</details>

<details>
<summary>typescript-eslint/typescript-eslint (@&#8203;typescript-eslint/parser)</summary>

### [`v5.52.0`](https://github.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#&#8203;5520-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5510v5520-2023-02-13)

[Compare Source](typescript-eslint/typescript-eslint@v5.51.0...v5.52.0)

**Note:** Version bump only for package [@&#8203;typescript-eslint/parser](https://github.com/typescript-eslint/parser)

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about these updates again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNC4xMzMuMCIsInVwZGF0ZWRJblZlciI6IjM0LjEzNi4wIn0=-->

Co-authored-by: cabr2-bot <cabr2.help@gmail.com>
Reviewed-on: https://codeberg.org/Calciumdibromid/CaBr2/pulls/1784
Reviewed-by: Epsilon_02 <epsilon_02@noreply.codeberg.org>
Co-authored-by: Calciumdibromid Bot <cabr2_bot@noreply.codeberg.org>
Co-committed-by: Calciumdibromid Bot <cabr2_bot@noreply.codeberg.org>
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
awaiting response Issues waiting for a reply from the OP or another party enhancement: plugin rule option New rule option for an existing eslint-plugin rule
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Enhancement: [explicit-function-return-type] add option to ignore IIFEs
4 participants