Open kokerinks opened 4 months ago
Thanks for bringing this up. I understand that accidentally running the 'clear' command can be disruptive, especially when it results in the removal of all test data from the application. However, this behavior is by design rather than a bug.
The 'clear' command is intended to give users a clean slate, which can be useful in various scenarios, such as preparing the environment for new tests or demonstrations without old data clutter.
Team chose [response.Rejected
]
Reason for disagreement: The explanation provided does not address the issue at hand. It only addresses the design choices made for the clear
command, and does not actually address the issue identified, which is the inconvenience of having to manually populate the application with multiple add commands.
If the user accidentally runs the clear command, the application will be left completely empty.
This is a huge inconvenience for the user, especially if they still wish to test out the commands on the application. They will have to manually add their own test members, which is very time-consuming.
Having a command to seed test data into the application is a very important function for this purpose, especially for first-time users of the application who are still experimenting with the application and do not yet know what they are doing.