Sismic

Latest version: v1.6.8

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

Scan your dependencies

Page 4 of 11

1.1.1

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

- (Fixed) Whitespaces in event parameters used in BDD steps are stripped before they are evaluated.

1.1.0

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

- (Added) ``Interpreter._select_event`` accepts an additional parameter ``consume`` that can be used
to select an event without consuming it.
- (Added) Documentation for extensions, and two (not included in Sismic!) extensions providing import/export
with AMOLA, and new semantics for the interpreter.
- (Fixed) Final states remain in the active configuration unless they are all children of the root state. In this
case, statechart execution is stopped. Previously, if all leaf states of the active configuration were final states,
the execution stopped even if these final states were nested in an orthogonal or compound state. The corrected
behavior strictly adheres to SCXML 1.0 semantics. This could be a backward incompatible change if you explicitly
relied on the previously wrong behaviour.

1.0.1

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

- (Fixed) BDD steps that involve a state raise a ``StatechartError`` if state does not exist.
This prevents *state X is active* (and its variants) to fail, e.g., because *X* is misspelled.

1.0.0

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

After more than two years of development, Sismic is stable enough to be released in version 1.0.0.
Consequently, Sismic will adhere to semantic versioning (see `semver.org <https://semver.org/>`__), meaning that
breaking changes will only occur in major releases, backward compatible changes in minor releases, and bug fixes in
patches.

0.26.9

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

- (Fixed) ``based_on`` for ``export_to_plantuml`` correctly takes into account states whose name contains whitespaces.
- (Fixed) ``export_to_plantuml`` properly exports transition with no event, no guard and no action.
- (Changed) ``export_to_yaml`` does not add quotes by default.

0.26.8

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

- (Added) ``import_from_yaml`` accepts a ``filepath`` argument.
- (Added) ``based_on`` and ``based_on_filepath`` parameters for ``export_to_plantuml`` so a previously generated
PlantUML file can be used as a basis for a new one (including its modifications related to the direction and length
of transitions).

Page 4 of 11

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.