[Code Review] Vavinan

[wwweert123]

Try not to say that the error is unknown, because in the PE all errors should be known and accounted for

In here, I don't think there is a need to check whether the data is a integer. This is because the Integer.parseInt method will automatically throw the number format exception if it fails

You should add some error handling here because the user might access out-of-bounds for the splitted string "parts"

Overall code looks organized but there are some parts where the function serve almost the same purpose as another. For example parseTransactionType and parseTransaction are the same except for the separator. Perhaps, more descriptive names can be used to differentiate the two or you could abstract the repeated logic out into another function.

[Vavinan]

1. It's for our debugging purpose to catch some unhandled error cases, we will remove that in our final product

2. We will consider this change in our future iterations

3. For this one the user input is received in way that it will prompt the user to type Transaction type first and then followed by other data one by one, where each data will be received separately. I have included the relevant function below. Correct me if I took the question wrongly.

Thank you.

[wwweert123]

Ok understood, then this should be fine!

[wwweert123]

Oh and I missed out something, Is the category always an integer as well,? because you did parseInt() which might cause an uncaught exception to be thrown

[Vavinan]

Yes, it will be an integer always. For now, it has been caught if other numbers or text is typed instead. I have attached one example below. We will make a check explicitly in our future iterations. Thank you for notifying this.