"non-explicit field transition" warning firing on inherited classes. about django-fsm HOT 8 CLOSED

There is a design problem with django-fsm

It is good to have explicit fields declaration, and support for multiple state fields in the same model. but it makes hard to design how it should looks with inheritance and proxy models.

from django-fsm.

I'm hitting this same problem. Is there any way to get rid of those warnings? Are they coming from Django or FSM itself?

from django-fsm.

@andresdouglas The warning comes from django-fsm itself (see https://github.com/kmmbvnr/django-fsm/blob/master/django_fsm/db/fields/fsmfield.py#L117)

from django-fsm.

@kmmbvnr I've been wondering about this and trying a couple of things out, but have had no luck. My first thought was to try to switch the field kwarg to being a string, and then using getattr(self, field) inside inner_transition, but that won't fly because we need to pass field into FSMField() before then (https://github.com/kmmbvnr/django-fsm/blob/master/django_fsm/db/fields/fsmfield.py#L123).

The other thing I might try, in my app, is to monkey-patch the subclass to redeclare the field from the base class, but that may cause Django to cry - and wouldn't be a pretty fix. Will let you know if that at least works - if it does, perhaps making @transition into a triple-nested decorator would work

from django-fsm.

Yep, think passing a string is a good and django-natural way to work on this issue, But some work on django-fsm internals need to be done. I have time now for doing that

from django-fsm.

Thanks @kmmbvnr, that's great to hear. If I can help, let me know.

from django-fsm.

I just started to learn generators and such today to try to have -fsm generating diagrams and ..._transitions... functions for proxies and inherited models.. Sadly python is not lisp (lol) and on top of that I have never created any own decorators so I'm on sketchy ground trying to figure things out. I mostly spent time learning about the basic python stuff so any pointers are welcome...

This is at least slightly related to this issue :) (I hope being quite drunk and all)

from django-fsm.

Inherited models drawing should works in version 2.0

from django-fsm.