Deprecate `:phoenix` atom as predefined plugin

[remi]

📖 Description and reason

Following @paveltyk’s suggestion in #28, let’s favor the use of CredoNaming.Check.Consistency.ModuleFilename.Plugins.Phoenix as our predefined plugin instead of the opaque :phoenix atom.

:phoenix is still supported for backward-compatibility.

🦀 Dispatch

#dispatch/elixir

[paveltyk]

@remi why do you want to limit plugins to only predefined plugins with when plugin in @plugins ? How do you feel about allowing any module that provides Behavior to be used? That will allow for greater flexibility.

Thank you for a great credo check :)

[paveltyk]

Will you please bump a version for new changes?

[remi]

@remi why do you want to limit plugins to only predefined plugins with when plugin in @plugins ? How do you feel about allowing any module that provides Behavior to be used? That will allow for greater flexibility.

Oh wait, that’s not what I wanted to do at all 🤦‍♂️ That doesn’t make sense. Let me fix this.

[paveltyk]

👍

[remi]

@paveltyk 2.1.0 was just released!

https://hex.pm/packages/credo_naming/2.1.0