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

Update DG (JY) #505

Conversation

jianyangg
Copy link

Updated implementation for register account in terms of:

  • Sequence diagram
  • Activity diagram
  • Their descriptive text

Close #503

Updated implementation for register account in terms of:
* Sequence diagram
* Activity diagram
* Their descriptive text
@jianyangg jianyangg added this to the V1.4 milestone Nov 11, 2023
@jianyangg jianyangg self-assigned this Nov 11, 2023
Copy link

codecov bot commented Nov 11, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (8e9d746) 84.35% compared to head (7c43f9b) 84.35%.
Report is 16 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #505   +/-   ##
=========================================
  Coverage     84.35%   84.35%           
  Complexity     1029     1029           
=========================================
  Files           121      121           
  Lines          3158     3158           
  Branches        370      370           
=========================================
  Hits           2664     2664           
  Misses          379      379           
  Partials        115      115           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link

@B-enguin B-enguin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some comments

1. The user specifies the `USERNAME`{.swift}, `PASSWORD`{.swift}, `CONFIRM_PASSWORD`{.swift}, `SECRET_QUESTION`{.swift}
and `ANSWER`{.swift} in the `register`{.swift} command.
1. If any of the fields is not provided, an error message with the correct command format will be shown.
1. If command parameters provided are not within the acceptable value range, an error message with the correct command format will be shown.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would value range sound abit wrong, since its not really a range?

Comment on lines +371 to +372
1. If not all fields are present, a `ParseException` is thrown saying incorrect command format.
1. If all fields are present, it checks if `PASSWORD`{.swift} and `CONFIRM_PASSWORD`{.swift} match.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would a check for password format be missing here?

Copy link

@Gabriel4357 Gabriel4357 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Gabriel4357 Gabriel4357 merged commit 35a4088 into AY2324S1-CS2103T-T13-3:master Nov 13, 2023
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update DG - Implementation (JY)
3 participants