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
The markVisited-attraction command seems to achieve the same result as executing "edit-attraction INDEX v/TRUE".
While this markVisited-attraction command may be more intuitive, it may also come across as a duplicate feature / unnecessary command since its purpose is already fulfilled by another command.
Furthermore, if a user wants to mark an attraction as not visited, there is no markUnvisited command or something similar, so the user will likely execute "edit-attraction INDEX v/FALSE", and in that case, since they are using the edit-attraction command to achieve this, it may seem odd that they use the markVisited-attraction command specifically to mark an attraction as visited but have to use a different command (edit-attraction) to mark is as not visited. At this point, they may be better off just achieving both results using the edit-attraction command.
The markVisited-attraction command seems to achieve the same result as executing "edit-attraction INDEX v/TRUE".
While this markVisited-attraction command may be more intuitive, it may also come across as a duplicate feature / unnecessary command since its purpose is already fulfilled by another command.
Furthermore, if a user wants to mark an attraction as not visited, there is no markUnvisited command or something similar, so the user will likely execute "edit-attraction INDEX v/FALSE", and in that case, since they are using the edit-attraction command to achieve this, it may seem odd that they use the markVisited-attraction command specifically to mark an attraction as visited but have to use a different command (edit-attraction) to mark is as not visited. At this point, they may be better off just achieving both results using the edit-attraction command.
Labels:
severity.Low
type.FeatureFlaw
original: shawn-nyk/ped#4
The text was updated successfully, but these errors were encountered: