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
MajorIndicates the severity or impact or benefit of an issue is much higher than normal but not critical.TaskIndicates an issue is neither a feature nor a bug and it's purely a "technical" change.wontfixIf you can reproduce this issue, please reopen the issue or create a new one describing it.
That is not a good idea if you ask me. The current convention works really great. If we rename the class to Plugin we would have an immediate conflict with \Piwik\Plugin which Plugin needs to extend from.
I think this really would be a poor decision to make. Right now we have a great convention naming the class after the folder!
Not really :( The autoloader expects the class to be in a file that matches the class name?
While it would be possible to change the autoloader, I don't see the benefit in doing this.. I really like the current convention we have. It is clear and easy to work with.
MajorIndicates the severity or impact or benefit of an issue is much higher than normal but not critical.TaskIndicates an issue is neither a feature nor a bug and it's purely a "technical" change.wontfixIf you can reproduce this issue, please reopen the issue or create a new one describing it.
To be consistent with API.php, Controller.php, Archiver.php, we should have the plugin main class' file be called Plugin.php
The text was updated successfully, but these errors were encountered: