You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A class constant should be used instead for best practice, ease of use and potentially less prone to typo mistakes etc.
This will not break any existing code as the plaintext will work fine too but I personally feel that being able to use a class constant is a more neater solution.
The text was updated successfully, but these errors were encountered:
Stupidly I forgot that the provider classes utilise the ProviderInterface and are looked up at runtime, therefore it would be silly to manage a static array of provider names given that my initial implementation was to have it dynamic.
A class constant should be used instead for best practice, ease of use and potentially less prone to typo mistakes etc.
This will not break any existing code as the plaintext will work fine too but I personally feel that being able to use a class constant is a more neater solution.
The text was updated successfully, but these errors were encountered: