New word-count plugin

The functional tests are now passing.
I added the missing schema and made the plugin a little more explicit in its handling of config data.

Thanks @tyler36 this is looking great. Hope it gets merged eventually.

Since the string separator is a fixed value (not to be changed for this plugin), I removed it as a setting from the plugin. Instead getSetting() gets overridden, so that it returns the separator that the Explode plugin asks for.

@jurgenhaas
Do you agree with these changes?

I still wonder if it is a good idea that this plugin extends the Explode plugin. I just reviewed ✨ Explode values as keys Needs work that adds a setting to the Explode plugin that makes no sense for the WordCount plugin to have.

Thanks @MegaChriz, I've looked at your changes and they really look nice.

I still wonder if it is a good idea that this plugin extends the Explode plugin.

Good question. If it were not extending that, there would be quite a bit of redundant code. On the other hand, I can see your point that further changes to the explode plugin could require extra attention in the word count plugin.

I can't really tell what's the better option, happy to leave that decision to yourself.

I made the WordCount plugin to no longer extend the Explode plugin and I merged the code!

Automatically closed - issue fixed for 2 weeks with no activity.