-
Notifications
You must be signed in to change notification settings - Fork 236
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
[CS2113T-T09-1] ConTech #24
base: master
Are you sure you want to change the base?
[CS2113T-T09-1] ConTech #24
Conversation
`Contact`. | ||
|
||
|
||
## <a name="implementation"></a>Implementation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think for each functionality, adding some sample inputs & outputs is much clear?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe you could use more types of UML diagrams in the DG. For example, object diagrams.
|
||
![Main Parser Sequence Diagram](images/MainParserSequenceDiagram.png) | ||
|
||
### <a name="command"></a>Command |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sections under “Design” seems not finished. Include “Command”, “ContactList”, and “TextUi”. Please fill them in soon.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the Command section can consider add in the Class diagram to relate all the commands together
|
||
![Edit Sequence Diagram](images/EditContactCommandSequenceDiagram.png) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ya, I agree with Mick. The diagram seems to be too big which causes the words inside the diagram a bit hard to see. You can try changing the maxMessageLength
of this diagram. Also you can consider putting new
before a Constructor()
call. :)
docs/DeveloperGuide.md
Outdated
|
||
## Instructions for manual testing | ||
## <a name="manual-test"></a>Instructions for manual testing | ||
|
||
{Give instructions on how to do a manual product testing e.g., how to load sample data to be used for testing} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe you could provide some instructions here for the manual testing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can consider to include some more class and object diagrams. Remember to add in the Object Deletion for the Command objects in your sequence diagrams. Overall a very detailed Developer Guide.
|
||
![Edit Sequence Diagram](images/EditContactCommandSequenceDiagram.png) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
`parseSearchQuery` and the `getDetailFlag` methods respectively. A `SearchContactCommand` with the specified parameters | ||
will be created and executed in `Duke`. The sequence diagram below shows how the whole process is carried out. | ||
|
||
![Search Sequence Diagram](images/SearchContactCommandSequenceDiagram.png) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The SearchContactCommand constructor have also not been called here
|
||
![Main Parser Sequence Diagram](images/MainParserSequenceDiagram.png) | ||
|
||
### <a name="command"></a>Command |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the Command section can consider add in the Class diagram to relate all the commands together
![Main Parser Sequence Diagram](images/MainParserSequenceDiagram.png) | ||
|
||
### <a name="command"></a>Command | ||
### <a name="contact-list"></a>ContactList |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code looks clear and understandable. It would be better if descriptions of methods can be provided.
import java.io.IOException; | ||
|
||
public class Storage { | ||
private final String contactFilePath; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[marcusbory] Maybe you should use all uppercase for constant.
} | ||
|
||
//@@author mayankp291 | ||
public static void missingArgEditMessage() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[mayankp291] Maybe you could name the method name as a verb. For example, printMissingArgEditMessage in this case. Similar naming issues can be seen in other methods.
//allow lowercase email ids | ||
String emailRegex = "^([\\w-\\.]+){1,64}@([\\w&&[^_]]+){2,255}.[a-z]{2,}$"; | ||
if (!detailToParse.matches(emailRegex)) { | ||
//LOGGER.log(Level.INFO, "Regex check for Email id failed"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[mayankp291] If you are not using this line of code for the LOGGER anymore, please delete it.
} | ||
|
||
//@@author ashrafjfr | ||
public static void helpMessage() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[ashrafjfr] Maybe you could name this method as an action. For example, printHelpMessage.
System.out.println(LINE); | ||
} | ||
|
||
public static void welcomeMessage() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[lezongmun] Maybe you could name the method as an action.
public static final String BUFFER = " "; | ||
|
||
boolean[] hasDeletedDetail(String userInput) throws InvalidFlagException, InvalidDeleteDetailException { | ||
boolean[] hasDeletedDetail = new boolean[7]; //all false by default |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[ng-andre] I do not really understand the design of the list of boolean variables for hasDeletedDetail. Could you please specify why the length is 7? Maybe avoid the usage of magic numbers.
User Guide upgrades
Fix formatting issue
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need add more details in some parts
![Sysem Architecture Sequence Diagram](images/SystemArchitectureSequence.png) | ||
|
||
|
||
### <a name="text-ui"></a>TextUi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Text-ui does not seem to be complete, along with Command and ContactList, maybe can try finish up the details soon
|
||
![Edit Sequence Diagram](images/EditContactCommandSequenceDiagram.png) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One way to solve this is by putting reference frame :D
docs/DeveloperGuide.md
Outdated
|
||
## Instructions for manual testing | ||
## <a name="manual-test"></a>Instructions for manual testing | ||
|
||
{Give instructions on how to do a manual product testing e.g., how to load sample data to be used for testing} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe can include some manual testing instructions?
`parseSearchQuery` and the `getDetailFlag` methods respectively. A `SearchContactCommand` with the specified parameters | ||
will be created and executed in `Duke`. The sequence diagram below shows how the whole process is carried out. | ||
|
||
![Search Sequence Diagram](images/SearchContactCommandSequenceDiagram.png) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix <QUERY> issue using escape sequence
Minor code refactor
|
||
![Edit Sequence Diagram](images/EditContactCommandSequenceDiagram.png) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ya, I agree with Mick. The diagram seems to be too big which causes the words inside the diagram a bit hard to see. You can try changing the maxMessageLength
of this diagram. Also you can consider putting new
before a Constructor()
call. :)
|
||
![Edit Sequence Diagram](images/EditContactCommandSequenceDiagram.png) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One way to solve this is by putting reference frame :D
# Conflicts: # src/main/java/seedu/command/ViewContactCommand.java
Update DG for formatting error
Add line break to marcusbory.md
PPP updates
Update to UG theme and ashraf PPP
Updated PPP and README
Update UG with new theme
Developer guide updates
Marcus PPP
Update ng-andre PPP
Update PPP
ConTech is a Command Line Interface (CLI) app for people in the computing industry (who prefer CLI) to manage computing-related contacts. It is optimised for CLI users so that they are able to access their contacts' information (ie Github ID, LinkedIn profile, Email, etc) quickly using commands.