API logging cleanup and new feature #86
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 3 commits
August 17, 2025 20:00
…ity to update via the name of the logging category.
…ls via the name of the log category.
…he database, for easy translation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR updates the logging API to allow identifying log settings not only by numeric ID but also by a predefined set of exact string names that match the entries in the database (e.g., "Verification Log", "Join Log", etc.).
Key Changes:
GET /logging endpoint can now accept either no parameter (returns all), an integer id, or a predefined string name to fetch a specific log setting.
PUT /logging/ endpoint accepts either an integer ID or a predefined name to update a log setting.
POST /logging endpoint enforces that new log settings can only be added with valid predefined names (matching DB names).
DELETE /logging/ endpoint supports deletion by either ID or predefined log name.
Updated DB helper with queries supporting both ID and exact name lookups for logging settings.
Allowed log names set updated to precisely match log names defined in the database initialization script, including spaces and capitalization.