Skip to content

[WIP] Investigate logging implementation in repository - #1

Draft
ch-arslanahmad with Copilot wants to merge 1 commit into
mainfrom
copilot/check-logging-implementation
Draft

[WIP] Investigate logging implementation in repository#1
ch-arslanahmad with Copilot wants to merge 1 commit into
mainfrom
copilot/check-logging-implementation

Conversation

Copilot AI commented Jan 13, 2026

Copy link
Copy Markdown

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

Original prompt

does this repo has logging or no


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

@ch-arslanahmad

Copy link
Copy Markdown
Owner

@copilot remove the branch and simply answer normally

Copilot AI commented Jan 13, 2026

Copy link
Copy Markdown
Author

@copilot remove the branch and simply answer normally

Based on my investigation of the repository:

No, this repository does not have formal logging implemented.

While the README mentions installing libspdlog-dev, the spdlog library is not actually included or used in the code. The codebase only has:

  • Basic error output using std::cerr in try-catch blocks (e.g., "Database error (tableExists): ...")
  • User-facing messages using std::cout and printf

There is no logging framework, no log levels, no log files, or structured logging of any kind - just console output for errors and user messages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants