Thanks for the PR,@Svish!

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 onhttps://opencollective.com/typescript-eslint

By the way, I don't know if I should also create an issue for this issue? That's what I considered to do to begin with, but since I realized it would be super easy to fix, I decided to just create a PR directly instead. But yeah... not sure what you want for project tracking purposes and such. 🤔

@bradzacher Cool! About updating the rule doc, I definitely could, but looking at it now, I'm not sure exactly what I should update. What it says there now is already correct.

if true, only functions which are part of a declaration will be checked

The check I've added isExportDefaultDeclaration, so it's covered by "part of a declaration". I suppose I could add my 1 valid and 2 invalid tests to the rule doc examples... Want me to do that? And are there other adjustments you think should be made? 🤔

I've added two examples of code that after this change will still be incorrect, even withallowExpressions set totrue. Not sure what else would make sense to add/change though...

As a minor cleanup of my own earlier PR, I also simplified the examples forallowHigherOrderFunctions by removing the function parameters. Looking at them again now, I realized they aren't actually relevant to the examples at all, so they are really just adding clutter.