Open lwlshawn opened 3 years ago
This is expected behaviour, since we want to always remind the user whenever they execute any commands regarding an elderly that has something that might be wrong. This is why we show a warning sign in the message.
Team chose [response.Rejected
]
Reason for disagreement: [replace this with your explanation]
When using edit to remove the lastvisit field, the application warns the user that a lastvisit date should be in the future. This happens when editing an elderly whose current visit date is wrong. Perhaps the warning should be kept to what happened in the current command?
I thought this might throw a user off slightly, as you are unable to edit the next visit field using the edit command, and are receiving an error unrelated to the command you have just executed.
To reproduce this, create an elderly with a lastvisit date, and a next visit date that is in the past, and use the command "edit INDEX lv/" to clear the last visit date