My question would be, is this setting actually sufficient for enabling more complex workflows? An important component of workflows I've seen in other frameworks is policies and enforcement. For instance, certain users are privileged to approve changing the status of content from one stage to another.
Right now, the content status represents a policy -- whether or not the content is public. It seems like the goal of your proposal is to also use content status as an arbitrary label. If this is correct I would argue that this data is different in kind and should therefore be in a different field. However, perhaps this label field could serve as a "wrapper" around the status -- hiding the field in the admin and setting it based on it's own internal logic. On Tue, Sep 20, 2016 at 11:45 PM, Eduardo Rivas <[email protected]> wrote: > There's another person working on something like this here: > https://github.com/stephenmcd/mezzanine/issues/411#issuecomment-235018090. > You may want to check on that and unify efforts. > > One issue with your approach is that it will require a migration when a > user adds a new choice. This will affect all models that subclass > Displayable (pretty much everything). The developer will have to maintain > the whole migration history separately or use one of the hacks for field > injection. Not desirable IMO. > > Maybe we can define the choices in the form level instead of the model? > That way the model field can be a non-choiced field while the dynamically > generated choices are used in the form. That will still require a single > migration but it can live in Mezzanine and be completely backwards > compatible. > > > -- > You received this message because you are subscribed to the Google Groups > "Mezzanine Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
