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
Hello, I'm doing some unittesting around a workflow which is enabled by django-enumfield enum __transitions__, and I'm seeing something unexpected. Suppose we had:
No AssertionError would raise! The status of the field will appear as UNREACHABLE, even though that should be impossible as the change did not pass validation. The behavior I expected was that the field value would be returned to it's pre-validation value (namely NEW). As I write this I'm realizing that the existing behavior permits bypassing validation, which may be a feature, and not a bug; so a change may not really be necessary.
Thanks for this package, it is great and necessary!
The text was updated successfully, but these errors were encountered:
Hello, I'm doing some unittesting around a workflow which is enabled by
django-enumfield
enum__transitions__
, and I'm seeing something unexpected. Suppose we had:Then, if I were to run something like:
No
AssertionError
would raise! The status of the field will appear asUNREACHABLE
, even though that should be impossible as the change did not pass validation. The behavior I expected was that the field value would be returned to it's pre-validation value (namelyNEW
). As I write this I'm realizing that the existing behavior permits bypassing validation, which may be a feature, and not a bug; so a change may not really be necessary.Thanks for this package, it is great and necessary!
The text was updated successfully, but these errors were encountered: