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.
Description
Inspired by discussion in #47 and the awesome work of @ticosax I drafted this solution (using codex).
It's probably not perfect but gives us a good support to discuss the target and the path to migrate.
As discussed previously, I'd like to kill 2 birds with one rock and make it possible to store all logs in a single table or having a dedicated table for each model to track.
I kept the centralized table (and its GenericForeignKey) but it's providing a "Bring your own model" where you can have a strong foreignkey.
Type of Change
Checklist
uv run pytestorpytest)uv run ruff check .)Testing
# Commands used to test uv run pytest tests/test_xxx.py -vRelated Issues