Customizable paths in config about tlint HOT 5 CLOSED

@ecrmnn will PR #288 work for you?

from tlint.

Thanks @driftingly

I'm pretty sure this solves our problem. Thanks a lot!

We've written a few custom rules as well, do you think it's best to keep them in our own separate package or would you like us to make PRs to TLint?

from tlint.

@ecrmnn This has been tagged v6.3.0.

For PRs, yes please, PRs are welcomed. Just keep in mind they may not get merged in (the tool is fairly opinionated), but it would be helpful to see what extra functionality you needed. There's a bit of a shift coming with the 7.0 release. This tool will leave a lot of sniffing/formatting to another tool where that tool is able: #284

from tlint.

We're using TLint in combination with PHP CS Fixer since we feel it lacks important rules. Just take NoCompact as an example, there isn't any equivalent in PHP CS Fixer as I know of.

What are you planning on removing?

Would be good to know so we don't invest time in a package that is going away or changed drastically.

from tlint.

We are removing lints and formatters that are covered by those other tools (Sniffer and Fixer) and focusing on what those tools cannot do.

from tlint.