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

[PE-D][Tester E] User guide does not specify the constraint for each command argument #121

Closed
soc-pe-bot opened this issue Apr 5, 2024 · 1 comment · Fixed by #169
Closed
Assignees
Milestone

Comments

@soc-pe-bot
Copy link

Description

The current user guide lacks clear specifications on the constraints for each parameter of the commands. Users are left uncertain about the expected formats and limitations of the values they can enter, which can lead to confusion and errors when attempting to use the application as intended.

Expected Behavior

The user guide should provide detailed information about the value constraints for each parameter of the commands. It should include the expected formats, acceptable value ranges, and any special formatting requirements. An ideal example is shown below for reference:
Correct Constraints Example

Actual Behavior

The documentation only outlines the command format and provides some examples without detailing the constraints for each parameter. The lack of this critical information can be observed in the current documentation screenshot below:
Current User Guide Screenshot

Additional Information

A specific instance of this issue is highlighted in feature flaw #6, where the add and edit commands accept numeric values for the interview time field, which is counterintuitive as the end user might expect a date format. Proper documentation regarding such constraints is crucial to prevent user confusion.


Labels: severity.Low type.DocumentationBug
original: jmsandiegoo/ped#4

@Lalelulilulela
Copy link

Specify constraints for each of the feature that each of us added previously
TianYao specify for the previous features such as name and email etc.

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

Successfully merging a pull request may close this issue.

6 participants