Skip to content

Conversation

@9hafidz6
Copy link

No description provided.

Copy link

@sanjukta99 sanjukta99 left a comment

Choose a reason for hiding this comment

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

Overall, good progress. Take a look at my suggestions.

You should follow the Java Coding Standards for JavaDoc comments and naming conventions. We also recommend that you delete commented out code as it makes the code more readable.

import java.util.List;

public class DishList {
private List<Dishes> dishlist;

Choose a reason for hiding this comment

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

Important that you write proper JavaDoc comments for all classes. You can find the Java Coding Standards on the module website


// public String toString() {
// return dishname;
// }

Choose a reason for hiding this comment

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

It's best to delete commented out code

import duke.ui.Ui;

public abstract class Cmd<T> {
public abstract void execute(T tasklist, Ui ui, Storage storage) throws DukeException;

Choose a reason for hiding this comment

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

Maybe using a more descriptive name like Command might be better?

private Dishes dish;
private int amount;
private int Nb;

Choose a reason for hiding this comment

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

What is Nb? Better to use a more descriptive name. That way even someone who's reading your code for the first time can understand what's going on in that part of the code

* Convert between String and Date.
*/
public class Convert {

Choose a reason for hiding this comment

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

Convert what? Consider renaming to something more descriptive

Fridge fridge = new Fridge();
@Test
void testPutIngredient() throws DukeException {
fridge = new Fridge();

Choose a reason for hiding this comment

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

Names for tests should follow the format featureUnderTest_testScenario_expectedBehavior(). Update accordingly for all the testcases

9hafidz6 and others added 26 commits October 31, 2019 19:06
* updated UG
implemented while loop in Duke class for Dish
modified parser to handle more errors
update Parser, Ui, and Duke main class.
to fix issues reported by PED run
2. Format order command to make sense and better user experience.
3. Add functions to check for valid date/month/year.
4. Fix update problem in setting an order date.
5. Extract Parser.parse function case "c" to several subfunctions--look neat.
6. Fix crashes when converting a string to date.
7. Fix small typo when printing out messages.
More neat order command and handle exceptions
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.

7 participants