.associateExtWithParser() instead of skipUnsupported

[ecarlisle]

First, thank you for this plugin! This has been very useful for me!

Leasot raises an exception when it encounters a file extension it does not support. Therefore the skipUnsupported option in todo-webpack-plugin doesn't add the ability to parse files not supported by leasot.

https://github.com/pgilad/leasot/blob/9af95b823cffa0b43289a3c9341158a1aef74554/lib/parsers.js#L98-L100

However there is the .associateExtWithParser(parsers) API that will allow explicit association of an unsupported like extension with a bundled parser.

https://github.com/pgilad/leasot#associateextwithparserparsers

I have files with unsupported extensions that could be associated with a bundled parser. I'd be happy to fork an submit a PR where the .associateExtWithParser(parsers) API was extended into todo-webpack-plugin.

How does this sound?

[mikeerickson]

@ecarlisle Thank you for the request, I will allocate some time to get it added. If you would like to PR it, that would be much appreciated 👍

[ecarlisle]

Great, thanks! Happy to help! This may be another issue, but should the skipUnsupported option be removed if leasot does not support it?

[ecarlisle]

Actually, we may want to instead plan to deprecate. If the skipUnsupported option is used, I can output a deprecation warning. I can also include that in the README.md docs as well.

[mikeerickson]

My preference would be to place deprecation warning in README.md and give enough warning for the next major release (will have minor release with the above mentioned feature)