Typo in configs

[justinyost]

https://github.com/loadsys/CakePHP-CreatorModifier/blob/master/src/Model/Behavior/CreatorModifierBehavior.php#L31

[justinyost]

This is pretty hard to change at this point without basically being a breaking change or having both options available. I'm not sure of a third solution.

Edit:

Option 1: Add a new version that hard breaks this and either break SemVer or release a new version that fixes this one thing.

Option 2: (Copied from @beporter's comment) New minor version that uses corrected key name but falls back to the improper naming. If that occurs, emits a php warning saying "deprecated name- please update your code, will be dropped in next release." And then New major version number, make sure to specifically call it out in release notes. No longer support the improper name.

[beporter]

How about:

1. New minor version that uses corrected key name but falls back to the improper naming. If that occurs, emits a php warning saying "deprecated name- please update your code, will be dropped in next release."
2. New major version number, make sure to specifically call it out in release notes. No longer support the improper name.

This is something I think ember got pretty correct. The beauty is that you can do both steps in quick succession and release both immediately. Anybody using the recommended version constraint will update to the version that throws warnings, but not to the breaking change version, which they can do as soon as they resolve the warnings in their own code.

And to boot: Anybody that hasn't overridden the default config explicitly or defined their own override method won't even notice the change, right?

[justinyost]

That was basically my idea for the having both options available. I obviously just shortcutted it in my head and didn't commit it to github.