The tests are all packed into one single executable. The more code is written, the more the single executable grows.

Find a way of breaking down the test executable into multiple compile units (AKA cpp files) or executables.

I'm running Ubuntu 22.10 with qt6-base and libspdlog-dev installed, running cmake .. -DBUILD_TESTING=ON -DBUILD_COVERAGE=ON runs fine, but running make afterwards (gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ) returns

[  0%] Built target qspdlog_interface
[  5%] Automatic MOC and UIC for target qspdlog_lib
[  5%] Built target qspdlog_lib_autogen
[ 11%] Automatic RCC for qspdlog_resources.qrc
[ 16%] Building CXX object src/CMakeFiles/qspdlog_lib.dir/qspdlog_lib_autogen/mocs_compilation.cpp.o
c++: error: unrecognized command-line option ‘-fprofile-instr-generate’; did you mean ‘-fprofile-generate’?
c++: error: unrecognized command-line option ‘-fcoverage-mapping’
make[2]: *** [src/CMakeFiles/qspdlog_lib.dir/build.make:88: src/CMakeFiles/qspdlog_lib.dir/qspdlog_lib_autogen/mocs_compilation.cpp.o] Fehler 1
make[1]: *** [CMakeFiles/Makefile2:182: src/CMakeFiles/qspdlog_lib.dir/all] Fehler 2
make: *** [Makefile:101: all] Fehler 2

Originally posted by @Overflwn in #32 (comment)

Description

Docker images are build with every PR and pushed with tag latest. It may bring issues when having multiple PRs in parallel running the workflow. It's required to fix this:

• docker images are pushed with different tags per PR
• the intermediate tags should be configured to auto-remove when the PR gets merged
• The PR should run on the corresponding image

The functionality will allow the user to assign a style to the logger, so the log messages from that particular logger will show up in a user-defined way. For example, with a red background and green foreground colors.

Check out the second table at Qt::ItemDataRole's documentation.

Description

As QSpdLog is a subclass of QTreeView and it derives publicly, it also derives the interface of the QTreeView, allowing the users to do dangerous things to its instance (e.g. changing the model).

Possible solutions

The class should derive from the QWidget class and have the QTreeView widget in it.

Description

To keep the code quality on high levels, an automated code coverage report should be configured.

In case of multiple loggers writing to the same sink(s) it's hard to differentiate which logger sent which message.

Personally, in projects where I have multiple threads for example, I like to create separate loggers writing to the same sinks so that I can quickly see which thread / "part of the system" logged what into the sinks without explicitly writing that into the log messages themselves.

I think simply adding a column for the logger names would be sufficient enough for this. I can add this and create a pull request for it, if you want to. As far as I can understand the code it's a very simple addition.

Maybe even adding a feature to hide specific columns would be a good idea as well? I'm not sure about that though.

If you handle the Qt messages to print those in the widget, the widget may report a Qt message internally while adding an entry, thus blocking the application execution. We need to somehow block all the Qt messages from the widget.

Description

As of now, the filtering and auto-scroll policy setup is done privately, by the toolbar widget which is provided by QSpdLog class. But as a user, one would want to construct their own toolbar and set it up.

Either the class should provide a way of registering their toolbar, or it should provide ways to call the required methods.

The functionality required for custom implementation is the following:

• filter (with options of case sensitivity, regular expression)
• auto-scroll

Possible solutions are:

• with the interface approach
  1. create a base interface class (e.g. QAbstractSpdLogToolBar)
  2. derive the default QSpdLogToolBar from it
  3. add a method in QSpdLog for registering a QAbstractSpdLogToolBar
• with methods exposure approach
  1. make the filter slot function public
  2. make the auto-scroll configuration setup slot function public