-
Notifications
You must be signed in to change notification settings - Fork 58
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
EDIT: Should not be able to save name choice 3 when name choice 2 is blank #126
Milestone
Comments
Could:
|
Going with 2 unless someone says otherwise |
This was referenced Feb 1, 2019
In the API we're also not handing it, so there's a new ticket, #136 |
After further discussion with @forgeuxGH5 on @katiemcgoff's feedback, we'll take the error message approach. So: |
This was referenced Mar 1, 2019
Kaineatthelab
added this to the Sprint 24 - Prepare for Coops and NameX for shut down March 8 milestone
Mar 1, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently when you edit name choices on a request that has only one name, you can enter a value in the 3rd field and leave the second field blank. This makes no sense.
I cannot imagine a valid case where my first choice would be "Acme", I have no second choice, but just in case my second choice is also unacceptable, please consider my third choice, "Roadrunner"
The text was updated successfully, but these errors were encountered: