Refactors the Gravatar implementation to be theoretically extensible, allowing other avatar providers (assuming they take the parameters of email, size and default image path).
Gravatar is currently used in the dashboard, so I moved it from the code all being in the controller to being in a Gravatar class, which is stored in a collection of avatar providers.
The reason for this is because blog comments makes use of Gravatar but I wanted to allow users to swap it out for similar avatar providers.
What does this do?
Refactors the Gravatar implementation to be theoretically extensible, allowing other avatar providers (assuming they take the parameters of email, size and default image path).
Gravatar is currently used in the dashboard, so I moved it from the code all being in the controller to being in a
Gravatarclass, which is stored in a collection of avatar providers.The reason for this is because blog comments makes use of Gravatar but I wanted to allow users to swap it out for similar avatar providers.
How should this be manually tested?
Related PRs / Issues / Resources?
Anything else to add? (Screenshots, background context, etc)