[IMPORTANT] Future of the library

[OwlyCode]

Hello,

It's been two years since I left the PHP/Symfony world and I almost certainly won't return in the coming years. I'm facing a difficult decision in regard of this library as I can no longer maintain it. I wish I could and I really wanted to at first, but I'm not a user of it anymore, and I don't even know what twig looks like nowadays.

I know @localheinz has done a lot in regard of the code quality, CI and workflow, but we are lacking contributions on features to stay up to date with twig's new features.

Meanwhile some new libraries are rapidly gaining traction and might provide an alternative, like https://github.com/VincentLanglet/Twig-CS-Fixer by @VincentLanglet that also features a fixer and is based on sniffs like phpcs (probably a much better approach than mine).

Is anyone wanting to step up and take responsibility of this library, or should I put it in EOL and redirect to another tool?

[VincentLanglet]

There are some rule in https://github.com/friendsoftwig/twigcs/tree/main/src/Rule that I currently don't have in https://github.com/VincentLanglet/Twig-CS-Fixer.
But if wanted I'll happy to merge PR to integrate them if that can help.

[Ciloe]

Hi @OwlyCode, many thanks for your hard work. I haven't got the time two, so I can't get the project.

@VincentLanglet I think it's a good idea to add the unused rules in your base code.

See ya !

[VincentLanglet]

Meanwhile some new libraries are rapidly gaining traction and might provide an alternative, like VincentLanglet/Twig-CS-Fixer by @VincentLanglet that also features a fixer and is based on sniffs like phpcs (probably a much better approach than mine).

For the record @OwlyCode, my tool is now quoted on the twig coding standard page https://twig.symfony.com/doc/3.x/coding_standards.html if it can help you on your decision.