Open fugimuse opened 1 year ago
If this seems like a good idea, I would be interested in taking it on and submitting a pull request.
Thanks @fugimuse for bringing this. Yeah, seems a good idea.
@fugimuse Is this in progress? I can make the change if no one has started yet.
@CleitonDeLima feel free to work on this
A slightly off-topic question: @hramezani how should I configure my environment correctly for this project? I configured venv
, pip install -e .
and pip install django
, run the tests with runtests.py/tox.
Is there anything else I need to configure? Sometimes I miss not having a manage.py
to create migrations, por example.
A slightly off-topic question: @hramezani how should I configure my environment correctly for this project? I configured
venv
,pip install -e .
andpip install django
, run the tests with runtests.py/tox. Is there anything else I need to configure? Sometimes I miss not having amanage.py
to create migrations, por example.
I also use the same setup. not sure what the problem is.
I also use the same setup. not sure what the problem is.
I created this draft, but I can't run the tests with a new CustomLogEntryModel
.
Maybe I configured the tests incorrectly.
I also use the same setup. not sure what the problem is.
I created this draft, but I can't run the tests with a new
CustomLogEntryModel
.Maybe I configured the tests incorrectly.
Thanks @CleitonDeLima for the PR and sorry for late reply! Unfortunatelly I am busy these days and can't help you a a lot to fix the problem.
Have you checked the CI error django.db.utils.ProgrammingError: relation "django_content_type" does not exist
?
you probably should be able to run the test easily by tox
e.g. tox -e py310-django50
I would like to be able to extend
LogEntry
with custom fields without introducing an additional table. I think this can be be accomplished by introducing a new classAbstractBaseLogEntry
, containing all of the code fromLogEntry
and adding:New fields could then be accommodated in the log as follows: