Patrick McElhaney

@dolsem How about we copy the three rules from this plugin into eslint-plugin-filename-rules, so that everyone can seamlessly switch? If you're interested, I'm happy to send a pull request.

The best way to fix this is probably to use cosmiconfig (#773)

Just found out about [lilconfig](https://github.com/antonk52/lilconfig) which has the parts of cosmiconfig that matter and zero dependencies.

I'm looking at this today.

This is a good idea. It wouldn't be part of the cli though. It would be part of the adapter, e.g., the [conventional changelog adapter](https://github.com/commitizen/cz-conventional-changelog). You can also create your...

I'm working on a tool that parses an OpenAPI spec and generates TypeScript for a dummy server. For example, the code I'm working on right now takes this: ```yaml openapi:...

However I think it would be great if there was an additional _synchronous_ function that outputs an inline type. I'd be okay with it not having some of the bells...

I hate it when _any_ rule lights up a whole function body. Part of the problem is it obscures other violations within the function body. Usually I prefer to identify...

> The problem with only highlighting the identifier is that it's pretty easy to miss. The fact that a function is getting too big is self-evident. If ESLint was only...

> And wouldn’t you just fix the error by reducing the max lines first and then fix any others you see? Because, as you said, that's a stylistic rule. I...