Xworkflows

Latest version: v1.0.4

Safety actively analyzes 629639 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 3

0.4.0

------------------

*New:*

* Improve support for transition hooks, with the :meth:`xworkflows.before_transition`,
:meth:`xworkflows.after_transition`, :meth:`xworkflows.transition_check`, :meth:`xworkflows.on_enter_state` and
:meth:`xworkflows.on_leave_state` decorators.

*Bugfix:*

* Fix support for inheritance of :class:`xworkflows.WorkflowEnabled` objects.

*Deprecated:*

* Use of the ``check=``, ``before=``, ``after=`` keyword arguments in the
``transition`` decorator is now deprecated; use ``before_transition``,
``after_transition`` and ``transition_check`` instead. Support for old
keyword arguments will be removed in 0.5.0.

*Backward incompatible:*

* The (private) :class:`~xworkflows.base.ImplementationWrapper` class no longer accepts the
``check``, ``before``, ``after`` arguments (use ``hooks`` instead)

0.3.2

------------------

*Bugfix:*

* Fix transition logging for objects whose __repr__ doesn't convert to unicode.

0.3.1

------------------

*Bugfix:*

* Make the :attr:`~xworkflows.base.State.title` argument mandatory in :class:`~xworkflows.base.State`
initialization

0.3.0

------------------

*New:*

* Allow and document customization of the :class:`~xworkflows.base.ImplementationWrapper`
* Add a method to check whether a transition is available from the current instance
* Cleanup :class:`~xworkflows.base.ImplementationList` and improve its documentation

0.2.4

------------------

*New:*

* Improve documentation
* Add pre-transition ``check`` hook
* Remove alternate :class:`~xworkflows.Workflow` definition schemes.
* Properly validate objects using two workflows with conflicting transitions.

0.2.3

------------------

*New:*

* Simplify API
* Add support for pe/post transition and logging hooks

Page 2 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.