feat: in-code specification of logging settings #115
Closed
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.
Notice
to test it before making changes to Concord.
What?
Add in-code specification of logging settings like logging level, filename, etc.
Why?
To satisfy issue #100
How?
I have done this by introducing two new main things:
discord_settings
)discord_settings_init
)The
discord_settings
structure will hold all of the in-code settings that should be used toinitialize a new client, while
discord_settings_init
function will apply those settings andinitialize a new client.
Testing?
Currently, I have not written any sanity checks for the contents of the settings array. That will be done
at a later time.