Open thisisaditya17 opened 1 week ago
While we understand your concern, the team believes that it is not necessary to list out all use cases and it is clear enough to show certain use cases that users might encounter. If we list out all types of use cases, it'll be too lengthy for the DG and reduce the value of making an effective DG.
Team chose [response.Rejected
]
Reason for disagreement: I understand the concern about keeping the DG concise, and I agree that an overly lengthy document could reduce its effectiveness. However, I believe that certain scenarios, such as the ability to delete an event after using the View or Filter command, are important to highlight because they represent key functionalities that users might encounter. Not mentioning them could lead to confusion or errors, especially if users are unaware of these possibilities.
If we follow the team's logic of excluding these use cases for brevity, then logically, the scenario for deleting after using the Find command could also be omitted. However, it was included because it’s a relevant and practical use case. I believe that similar use cases, like deleting after using View or Filter, should be treated with the same level of importance for clarity.
While I agree that not every use case needs to be listed, including these specific scenarios would enhance the clarity of the DG and improve the user experience by ensuring all relevant actions are documented.
Right now it doesn't mention it.
But deletion can happen after using view command
You can do it with Filter command too. Use case should consider these scenarios as well.