search

ArtillerySun / pe

0 stars 0 forks source link

The "help" command can only work with internet connection #3

Open ArtillerySun opened 2 weeks ago

ArtillerySun commented 2 weeks ago

image.png

when enter the command help, the software will redirect it into the browser and show the online user guide, however, I think add an offline support for the help command would be better for users without an internet connection, otherwise they cannot use the software without internet for the first time.

nus-pe-bot commented 1 week ago

Team's Response

Duplicate of #3642

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Entering help opens a window in browser

Screenshot 2024-11-15 at 5.33.59 PM.png Screenshot 2024-11-15 at 5.33.59 PM

steps to reproduce: enter help in the command line

as this is an app that does not need wifi or internet to run, it is quite a large inconvenience that inputting help will open a browser that requires the internet. for example, if someone is a first-time-user and is unfamiliar with how the app works but is outside and does not have wifi/internet, the user cannot use the app or can barely use it as help is unavailable. hence, this is marked as severity high.

edit: this is my last bug, just wanted to say ur app is really cute and I love that it is so pink and fit-for-user in terms of aesthetics. it was super hard to catch bugs btw.

[original: nus-cs2103-AY2425S1/pe-interim#3073] [original labels: type.FeatureFlaw severity.High]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

It is not a tP constraint to have an application that can fully function without internet connection. Furthermore, it was stated in the UG that a stable internet connection is required to access the user guide via the help command.

We feel that severity should be lowered to medium, since the in-app error messages are fairly detailed already to help most users continue using the app smoothly, minimising inconvenience to users.

All in all, we believe that this is beyond the scope in our current iteration but it can be a potential enhancement to be performed in future iterations

Items for the Tester to Verify

:question: Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

Reason for disagreement: [replace this with your explanation]

## :question: Issue response Team chose [`response.NotInScope`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
## :question: Issue type Team chose [`type.FeatureFlaw`] Originally [`type.FunctionalityBug`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]