Use dataclass for ExecNode in order to facilitate reading the code.
We should avoid validating the type of attributes if the type is boolean. We can be happy by using the Truthy value of the attribute. This should never fail for users
this is why the following code was removed:
if not isinstance(self.is_sequential, bool):
raise TypeError(
f"is_sequential should be of type bool, but {self.is_sequential} provided"
)
if not isinstance(self.debug, bool):
raise TypeError(f"debug must be of type bool, but {self.debug} provided")
if not isinstance(self.setup, bool):
raise TypeError(f"setup must be of type bool, but {self.setup} provided")
Fixes # (issue)
Type of change
[X] Bug fix (non-breaking change which fixes an issue)
Checklist:
[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
Description
Use dataclass for ExecNode in order to facilitate reading the code.
We should avoid validating the type of attributes if the type is boolean. We can be happy by using the Truthy value of the attribute. This should never fail for users
this is why the following code was removed:
Fixes # (issue)
Type of change
Checklist: