You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the situations I ran into is running trial transitions on non-permanent objects (i.e. not saved in the DB only memory) so they have no pk as of yet, however the fsm-log signal/creation that runs doesn't check for a pk before running manager.create(**values).
Is there a way of disabling the fsm_log decorator when there is no pk or some other way of manually saving without it running?
Alternatively, would a change that checks for a pk before running create() be a reasonable adjustment?
Just after posting, I realized this is happening on my transition methods that aren't even decorated by the fsm_log decorator so I'm at a bit of a loss as to how to disable it.
The text was updated successfully, but these errors were encountered:
One of the situations I ran into is running trial transitions on non-permanent objects (i.e. not saved in the DB only memory) so they have no pk as of yet, however the
fsm-log
signal/creation that runs doesn't check for apk
before runningmanager.create(**values)
.Is there a way of disabling the
fsm_log
decorator when there is nopk
or some other way of manually saving without it running?Alternatively, would a change that checks for a
pk
before runningcreate()
be a reasonable adjustment?Just after posting, I realized this is happening on my
transition
methods that aren't even decorated by thefsm_log
decorator so I'm at a bit of a loss as to how to disable it.The text was updated successfully, but these errors were encountered: