[CS2113T-T09-1] ConTech#24
Conversation
| `Contact`. | ||
|
|
||
|
|
||
| ## <a name="implementation"></a>Implementation |
There was a problem hiding this comment.
i think for each functionality, adding some sample inputs & outputs is much clear?
Mick609
left a comment
There was a problem hiding this comment.
Maybe you could use more types of UML diagrams in the DG. For example, object diagrams.
|
|
||
|  | ||
|
|
||
| ### <a name="command"></a>Command |
There was a problem hiding this comment.
Sections under “Design” seems not finished. Include “Command”, “ContactList”, and “TextUi”. Please fill them in soon.
There was a problem hiding this comment.
For the Command section can consider add in the Class diagram to relate all the commands together
| array with the details to be edited. An `EditContactCommand` with the specified parameters will then be created and | ||
| executed in `Duke`. The sequence diagram below shows how the whole process is carried out. | ||
|
|
||
|  |
There was a problem hiding this comment.
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. :)
| ## 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.
Maybe you could provide some instructions here for the manual testing?
| array with the details to be edited. An `EditContactCommand` with the specified parameters will then be created and | ||
| executed in `Duke`. The sequence diagram below shows how the whole process is carried out. | ||
|
|
||
|  |
| `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. | ||
|
|
||
|  |
There was a problem hiding this comment.
The SearchContactCommand constructor have also not been called here
|
|
||
|  | ||
|
|
||
| ### <a name="command"></a>Command |
There was a problem hiding this comment.
For the Command section can consider add in the Class diagram to relate all the commands together
|  | ||
|
|
||
| ### <a name="command"></a>Command | ||
| ### <a name="contact-list"></a>ContactList |
Mick609
left a comment
There was a problem hiding this comment.
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.
[marcusbory] Maybe you should use all uppercase for constant.
| } | ||
|
|
||
| //@@author mayankp291 | ||
| public static void missingArgEditMessage() { |
There was a problem hiding this comment.
[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.
[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.
[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.
[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.
[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
|  | ||
|
|
||
|
|
||
| ### <a name="text-ui"></a>TextUi |
There was a problem hiding this comment.
Text-ui does not seem to be complete, along with Command and ContactList, maybe can try finish up the details soon
| array with the details to be edited. An `EditContactCommand` with the specified parameters will then be created and | ||
| executed in `Duke`. The sequence diagram below shows how the whole process is carried out. | ||
|
|
||
|  |
There was a problem hiding this comment.
One way to solve this is by putting reference frame :D
| ## 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.
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. | ||
|
|
||
|  |
Fix <QUERY> issue using escape sequence
Minor code refactor
| array with the details to be edited. An `EditContactCommand` with the specified parameters will then be created and | ||
| executed in `Duke`. The sequence diagram below shows how the whole process is carried out. | ||
|
|
||
|  |
There was a problem hiding this comment.
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. :)
| array with the details to be edited. An `EditContactCommand` with the specified parameters will then be created and | ||
| executed in `Duke`. The sequence diagram below shows how the whole process is carried out. | ||
|
|
||
|  |
There was a problem hiding this comment.
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.