User Guide claimed to use add-task [t/TASK_NAME], when to add a task, we have to use add-task[tn/TASK_NAME]. The application itself will tell you to use tn/TASK_NAME and throw an error when using t/TASK_NAME.
Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-10-24 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.
Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-10-03 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.
I tried the assign-member ti/1 mi/AS command under the quick start section but it didn’t work. It looks like the syntax was updated sometime after the quick start section was written and the syntax in that portion of the user guide was overlooked. The updated command syntax works correctly so it’s probably just a matter of updating the Quick Start section of the user guide.
The first image shows the result of copying the assign member command from the quick start section of the user guide.
The second image shows that the command works with the updated syntax.
Medium severity since it is the example command given at the very start of the user guide.
A member's name gets truncated if it is too long. The fix should be pretty similar to the one in Duke where long commands/reponses were also getting truncated. A possible fix is to use the setWrapText method or the wrapText attribute in FXML.
When adding a task, if the name is too long, it will appear as cut-off instead of provindg wrapping text. Users will not be able to see if the task appears too long.
Create a settings page, complete with labels of each setting that the user can customise (if possible will include toggle switches that are responsive to user's settings command)
Light/Dark theme switch
12/24 hour display format
Reminder scheduling for upcoming tasks (moved to 1.4)
Since most of the data required for features is retrieved from the relevant filteredLists in Logic, e.g. filteredMembersList, the data is dependant on the current Predicate applied.
If user enters find-task nonsense, the filteredTaskList will be empty as nonsense doesn't exist. However this affects all components that are reliant on existing tasks. For example, if user enters assign-member ti/1 mi/JD, command result shown is Task id is not valid.
May need to restructure the way data is fetched for the UI.
Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-10-17 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.
Guys, it looks like your tP is maintaining a high-level of coding activities so far and all members are actively contributing (as per the tP Dashboard) 👍
Note: hope you can work together to help less-active team members, if they need help.
Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-09-19 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.
Guys, you have a file named \ that is causing problems for RepoSense. The file doesn't seem to be serving any legitimate purpose. Please rename or remove it ASAP.
Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-10-31 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.
Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-10-10 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.