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
{{ message }}
This repository has been archived by the owner on Mar 5, 2023. It is now read-only.
Rather, it should show the current filtered list + the added person.
We should not add the new person to the filtered list if the new person does not match the filter cirteria though.
On second thoughts, perhaps the current behavior is not that bad. In some cases the user may no longer be interested in the previous filtered list. If he is, he can use the 'up' button to run the previous find command.
Something I would like to do though is to be able to highlight the person that was just edited/added/deleted, for a few seconds. I think that too might require a change to the model architecture, possibly requiring another 'view model' layer. The filtered list too should be part of that layer. The current model should be reserved for keeping the 'one source of truth' that we save to the storage.
In some cases the user may no longer be interested in the previous filtered list.
I guess it's a bit hard to argue for the use case because we don't really have a user base to find out which behavior they prefer :P
Something I would like to do though is to be able to highlight the person that was just edited/added/deleted, for a few seconds. I think that too might require a change to the model architecture, possibly requiring another 'view model' layer.
AddCommand
should not updateModel
's filtered list to show all. Rather, it should show the current filtered list + the added person.The text was updated successfully, but these errors were encountered: