Added Config object #65
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
I don't know if this might be needed, but I've added a Config class to the project that can be passed instead of an array when initializing some of the library's objects. This offers several advantages over using an array as a configuration format:
Originally, I had planned to change the internal config variable used by all classes in this library to the Config class, but this could cause a breaking change due to the
getConfig($key)
method (since some users might use arrays for more options than this library provides). For now, this PR doesn't alter any existing behavior and simply adds the option of passing configuration values as a Config instance. If you like this change I could alter the code to use this class instead of array in the future (of course this change can still support passing the config as an array).