Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incomplete feature as users are unable to list rules #7

Open
ChenJiehan318 opened this issue Nov 15, 2019 · 1 comment
Open

Incomplete feature as users are unable to list rules #7

ChenJiehan318 opened this issue Nov 15, 2019 · 1 comment

Comments

@ChenJiehan318
Copy link
Owner

compared to other features such as problems, plans and tags that have command "listprob/plan/tag" to view the current list of the respective fields, there are no "listrule" command that allows the user to view the current rules in the rule list. Users can only view the rules via the tab in the gui, which is inconvenient and very easily missed out because the default size of the application is very small.

As a result, when the user wants to edit or delete a rule, they are unable to do so because they are unable to view the index of the rule to perform the respective action.

Screenshot 2019-11-15 at 5.10.22 PM.png

@nus-pe-bot
Copy link

Team's Response

  1. Default size of the application is not small, the compaction of the third and fourth tab is due to Mac’s DPI feature - the logical resolution of the screen may be below 720p.
  2. The reason why problems and plans have list command is that they support find command - by applying find, the list will be reduced and we have to find a way of listing all entries again. However, in the case of find rules, currently no findrule command is implemented, the find rule list always shows all find rules, there is naturally no need to add listfindrule command to make the command set more complicated. (Reject reason)
  3. Moreover, we provide CLI commands to switch tabs, considering the fact that we also have shorter versions for switchtab, which spells st tt/1 i/4, it’s even shorter than listfindrule (Downgrade reason)

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

  • I disagree

Reason for disagreement: [replace this with your reason]


❓ Issue severity

Team chose [severity.Low].
Originally [severity.High].

  • I disagree

Reason for disagreement: [replace this with your reason]


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants