Splitting the Code from the Configuration Dilemma
Every week I get new requests to add built-in support to more and more OAuth servers.
Having the configuration of each server built-in the class is the simplest way to use it for most users.
So something is necessary to change to move the configuration from the class code and still keep it simple.
My idea is to move the configuration of least popular servers to a separate file that will be read by the class if one server is used from those that are not on the built-in supported list.
That file will be probably in the JSON format, so it is easy to edit for users that want to add support to new servers.
Survey About Which Servers Will be Moved the External Configuration File
Moving the configuration of the least popular servers is the way to avoid affecting too many of the users. So the question is more on what are the least popular servers? I know that some servers are popular but I don't know about the rest.
Therefore I would like to ask you to help telling me which are the popular servers by filling this quick survey. You should just check one or more OAuth servers that you use. I will move the least picked servers to the separate configuration file.
Other Improvement Suggestions
The survey form also has an optional field to let you tell about other OAuth servers you would like to be supported in future versions.
There is also another optional field to let you describe any other features that you would like to see in the future.
If you would like to get a response to your suggestion, there is an optional field to let you enter your email address.
For other comments, please reply to this article here.
