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.

Sign up for GitHub

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

Jump to bottom

[1][ariesjia] Better form field validation #460

Closed
wmbutler opened this issue Sep 27, 2017 · 2 comments
Closed

[1][ariesjia] Better form field validation #460

wmbutler opened this issue Sep 27, 2017 · 2 comments
Labels
[3] Bug Classification indicating the existing implementation does not match the intention of the design [4c] High Priority Priority indicating significant impact to system/user -OR- workaround is prohibitivly expensive
Milestone
171001

Comments

@wmbutler
Copy link
Contributor

Closed #459 in order to create an actionable item:

  • Should fail validation if account does not exist
  • Should fail validation if non-numeric value is present in qty

validate
@wmbutler wmbutler added the [3] Bug Classification indicating the existing implementation does not match the intention of the design label Sep 27, 2017
@wmbutler wmbutler added this to the 171001 milestone Sep 27, 2017
@ariesjia
Copy link
Contributor

can i take this issue .

@wmbutler wmbutler changed the title [1] Better form field validation [1][ariesjia] Better form field validation Sep 28, 2017
@wmbutler
Copy link
Contributor Author

Yes, can you please knock it out today? Really want this in the current sprint.

@wmbutler wmbutler added the [4c] High Priority Priority indicating significant impact to system/user -OR- workaround is prohibitivly expensive label Sep 28, 2017
@ariesjia ariesjia mentioned this issue Sep 28, 2017
Merged
@svk31 svk31 closed this as completed in 0e435a5 Sep 29, 2017
@svk31 svk31 mentioned this issue Oct 1, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
[3] Bug Classification indicating the existing implementation does not match the intention of the design [4c] High Priority Priority indicating significant impact to system/user -OR- workaround is prohibitivly expensive
Projects
None yet
Milestone
171001
Development

No branches or pull requests
2 participants
@wmbutler @ariesjia