You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead or raising builtin Python exceptions (ValueError, etc), custom RAFCON ValidityException should be raised in their proper subclasses (e.g. DataPortTypeMismatchException).
This would e.g. allow to write more future-safe code then e.g. the following example from state_element.py: if "not have matching data types" in message:
Originally created by @franzlst ([email protected]) at 2019-07-15 13:16:42+00:00 (moved from RMC internal repository)
This discussion was converted from issue #760 on December 13, 2024 12:57.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Instead or raising builtin Python exceptions (
ValueError
, etc), custom RAFCONValidityException
should be raised in their proper subclasses (e.g.DataPortTypeMismatchException
).This would e.g. allow to write more future-safe code then e.g. the following example from
state_element.py
:if "not have matching data types" in message:
Originally created by @franzlst ([email protected]) at 2019-07-15 13:16:42+00:00 (moved from RMC internal repository)
Beta Was this translation helpful? Give feedback.
All reactions