django-fsm-dynamic 1.1.0

Dynamic workflow extensions for django-fsm-2

Django FSM Dynamic

Dynamic workflow extensions for django-fsm-2 that allow optional Django apps to modify FSM state machines without creating database migrations.

Features

• Dynamic State Enums: Extend state enums at runtime without migrations
• Callable Choices: Prevent Django from generating migrations when choices change
• Transition Builder: Programmatically create FSM transitions
• Workflow Extensions: Structured app-based workflow modifications
• Migration-Free: All extensions work without requiring database migrations

Installation

pip install django-fsm-dynamic

Requirements:

• Python 3.10+
• Django 5.0+
• django-fsm-2 4.0+

Quick Start

1. Create a Dynamic State Enum

from django_fsm_dynamic import DynamicStateEnum
from django_fsm import FSMIntegerField
from django.db import models

class BlogPostStateEnum(DynamicStateEnum):
    NEW = 10
    PUBLISHED = 20
    HIDDEN = 30

class BlogPost(models.Model):
    title = models.CharField(max_length=200)
    state = FSMIntegerField(
        default=BlogPostStateEnum.NEW,
        choices=BlogPostStateEnum.get_choices  # Prevents migrations!
    )

2. Extend from Another App

# In your review app's apps.py
from django.apps import AppConfig
from django_fsm_dynamic import WorkflowExtension, TransitionBuilder

class ReviewWorkflowExtension(WorkflowExtension):
    target_model = 'blog.BlogPost'
    target_enum = 'blog.models.BlogPostStateEnum'
    
    def extend_states(self, enum_class):
        enum_class.add_state('IN_REVIEW', 15)
        enum_class.add_state('APPROVED', 17)
    
    def extend_transitions(self, model_class, enum_class):
        builder = TransitionBuilder(model_class)
        builder.add_transition('send_to_review', enum_class.NEW, enum_class.IN_REVIEW)
        builder.add_transition('approve', enum_class.IN_REVIEW, enum_class.APPROVED)
        builder.build_and_attach()

class ReviewConfig(AppConfig):
    name = 'review'
    
    def ready(self):
        ReviewWorkflowExtension(self).apply()

3. Use the Extended Workflow

# Create a blog post
post = BlogPost.objects.create(title="My Post", state=BlogPostStateEnum.NEW)

# Use dynamically added transitions
post.send_to_review()  # NEW -> IN_REVIEW
post.approve()         # IN_REVIEW -> APPROVED

Core Components

DynamicStateEnum

Base class for extensible state enums:

from django_fsm_dynamic import DynamicStateEnum

class MyStateEnum(DynamicStateEnum):
    NEW = 10
    PUBLISHED = 20

# Other apps can extend:
MyStateEnum.add_state('IN_REVIEW', 15)

# Get all choices including dynamic ones:
choices = MyStateEnum.get_choices()  # [(10, 'New'), (15, 'In Review'), (20, 'Published')]

Dynamic Choices

Use the get_choices method directly to prevent Django migrations:

class MyModel(models.Model):
    state = FSMIntegerField(
        default=MyStateEnum.NEW,
        choices=MyStateEnum.get_choices  # No migrations when enum changes!
    )

TransitionBuilder

Programmatically create FSM transitions:

from django_fsm_dynamic import TransitionBuilder

builder = TransitionBuilder(MyModel)
builder.add_transition(
    'approve', 
    source=MyStateEnum.IN_REVIEW,
    target=MyStateEnum.APPROVED,
    conditions=[lambda instance: instance.is_valid()],
    permission='myapp.can_approve'
).build_and_attach()

WorkflowExtension

Structured approach to extending workflows:

from django_fsm_dynamic import WorkflowExtension

class MyExtension(WorkflowExtension):
    target_model = 'app.Model'
    target_enum = 'app.models.StateEnum'
    
    def extend_states(self, enum_class):
        enum_class.add_state('NEW_STATE', 99)
    
    def extend_transitions(self, model_class, enum_class):
        # Add new transitions
        pass
    
    def modify_existing_transitions(self, model_class, enum_class):
        # Modify existing transitions
        pass

Testing

Quick Testing (Single Environment)

• Run all tests: python -m django test --settings=tests.settings (from project root)
• Run specific test: python -m django test tests.test_dynamic_utilities --settings=tests.settings
• Run with coverage: coverage run -m django test --settings=tests.settings && coverage report

Matrix Testing (Multiple Python/Django Versions)

This project supports testing across multiple Python (3.10-3.14) and Django (5.0-5.2) versions using nox:

• Install testing dependencies: uv pip install -e .[dev]
• Run all stable test combinations: nox
• Run tests for specific Python version: nox -s tests-3.12
• Run tests for specific Django version: nox -s tests-3.12 -- --django=5.2
• Run experimental tests (Python 3.14, Django main): nox -s tests_experimental_python tests_experimental_django
• Run linting: nox -s lint
• Run formatting check: nox -s format
• Run coverage report: nox -s coverage

Available Python Versions

The project is tested against:

• Stable: Python 3.10, 3.11, 3.12, 3.13
• Experimental: Python 3.14 (allowed to fail)

Available Django Versions

The project is tested against:

• Stable: Django 5.0, 5.1, 5.2
• Experimental: Django main branch (allowed to fail)

Documentation

• Complete Documentation
• API Reference
• Examples

Why Separate Package?

Dynamic workflows are a powerful but specialized feature. By extracting them into a separate package:

1. Focused Development: Each package has a clear, focused scope
2. Optional Dependency: Only install if you need dynamic workflows
3. Independent Versioning: Features can evolve independently
4. Cleaner Core: django-fsm-2 stays focused on core FSM functionality

Contributing

We welcome contributions! Please see our Contributing Guide for details.

License

MIT License. See LICENSE for details.

Changelog

See CHANGELOG.md for version history.