Describe the bug 🐛
Full crash if effort is set to an empty (null) value. This applies for both empty inputs and an input of value 0, but not negative numbers.
PendingRollbackError: This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first
issue Session.rollback(). Original exception was: (sqlite3.IntegrityError) NOT NULL constraint failed: todo.effort
[SQL: UPDATE todo SET effort=? WHERE todo.id = ?]
[parameters: (None, 4)]
(Background on this error at: https://sqlalche.me/e/20/gkpj) (Background on this error at: https://sqlalche.me/e/20/7s2a)
NOTE: 1 of 2 errors shown. Run with textual run --dev to see all errors.
To Reproduce 🐣
Set the effort to a null value (empty or 0) and observe crash
Expected behavior 🤔
Values should ideally be set to the default state if null or a 0 is inputted, or at least reject the input to prevent a crash. If a value of 0 is not allowed, the default value should probably not be 0; otherwise, 0 inputs should be permitted and null inputs should result in a 0.
Desktop (please complete the following information): 🤖
- Arch Linux
- Kitty terminal (zsh)
- Hyprland WM
- Dooit v3.2.0
Describe the bug 🐛
Full crash if effort is set to an empty (null) value. This applies for both empty inputs and an input of value 0, but not negative numbers.
To Reproduce 🐣
Set the effort to a null value (empty or 0) and observe crash
Expected behavior 🤔
Values should ideally be set to the default state if null or a 0 is inputted, or at least reject the input to prevent a crash. If a value of 0 is not allowed, the default value should probably not be 0; otherwise, 0 inputs should be permitted and null inputs should result in a 0.
Desktop (please complete the following information): 🤖