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
Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.
I believe Filtering should be the same as the FIND command, which is already labelled further below in the user guide. This may be potentially confusing for readers.
Hi, our team believes that this is not an issue for the following reasons:
It is technically true that find and findcom commands filter the list that the user sees. So the commands do filter the displayed list. You also agree that "Filtering" means the find command, which supports our point that these two words are quite equivalent.
The target audience of the DG are developers. Many common languages all have some kind of filter command - Java has stream.fliter(), Python has filter, JavaScript has Array.filter()... So we believe that the word filter is quite commonly known by developers and this should not pose an issue.
Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.
I believe Filtering should be the same as the FIND command, which is already labelled further below in the user guide. This may be potentially confusing for readers.
[original: nus-cs2103-AY2223S1/pe-interim#5764] [original labels: severity.VeryLow type.DocumentationBug]
The text was updated successfully, but these errors were encountered: