Why lock entire plugin with private etc?
First when I found this plugin I thought that it was great. Didn’t look inside the code, just picked the function and everything was fine.
However, now I do have an issue, as someone not only want the users tweets, but an entire list.
I can understand that the plugin don’t have this or all other features out of the box, and I thought that I could just extend the class to add the functionality I wanted. However, as pretty much everything is using the prefix private, it is not possible to create a decent extension. I also noticed that everything else is pretty locked up as well.
If the plugin really are for developers, it should be flexible and easy to extend. My suggestion is to make it easier for others to use same authentication process in order to do other requests as well. One step towards this is to change those private parts to protected etc.
- The topic ‘Why lock entire plugin with private etc?’ is closed to new replies.