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

Adding spaces to time input to addExpense command results in wrong time format #5

Open
Arif-Khalid opened this issue Apr 14, 2023 · 1 comment

Comments

@Arif-Khalid
Copy link
Owner

Arif-Khalid commented Apr 14, 2023

I suggest warning the users about this specific error or accepting additional spaces since spaces are specified as the correct delimiter.
image.png

@nus-se-script
Copy link

nus-se-script commented Apr 18, 2023

Team's Response

This is an intended behavior of our product. We did state that the format for time is 'YYYY MM DD HH mm'. So entering additional spaces between the numbers will cause an error as it is not following the format we stated. In our next iteration we can perhaps solve this problem by allowing multiple spaces between numbers. But for this version, we are standardizing the space between numbers to be one.

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

  • I disagree

Reason for disagreement: By your very claim that this is something you can work on in your next iteration, you agree that this should be a behaviour that is worked on, thus, this should be response.notInScope over rejected.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants