We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently the field keyword argument in the signal handler is not being handled.
field
Therefore, if multiple state fields (e.g. "state" and "second_state") are being used those cannot be easily distinguished in the logs.
Do you think it makes sense to add "field_name" to StateLog, where kwargs['field'].name would be stored into?
StateLog
kwargs['field'].name
This could also be used in __str__ then, but is typically redundant then (since often only a single state field is used probably).
__str__
The text was updated successfully, but these errors were encountered:
This wouldn't be hard but does django-fsm actually send a field kwarg? It's not documented here: https://github.com/kmmbvnr/django-fsm#signals
django-fsm
Also, since transitions always refer to a specific field, you can just do getattr(Model, transition)._django_fsm.field to get to it later.
getattr(Model, transition)._django_fsm.field
Sorry, something went wrong.
No branches or pull requests
Currently the
field
keyword argument in the signal handler is not being handled.Therefore, if multiple state fields (e.g. "state" and "second_state") are being used those cannot be easily distinguished in the logs.
Do you think it makes sense to add "field_name" to
StateLog
, wherekwargs['field'].name
would be stored into?This could also be used in
__str__
then, but is typically redundant then (since often only a single state field is used probably).The text was updated successfully, but these errors were encountered: