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

Picklist Size Limit form validation error #4206

Closed
bronwyncombs opened this issue Nov 13, 2023 · 2 comments
Closed

Picklist Size Limit form validation error #4206

bronwyncombs opened this issue Nov 13, 2023 · 2 comments
Labels
1 - Bug Incorrect behavior of the product 2 - Forms Issues that are related to the form system

Comments

@bronwyncombs
Copy link

Describe the bug
The business rule for picklist size limit was removed a while ago (PR #2202), but the picklist form definition still enforces a size limit within the range of 2-500 to save. This leads to a weird UX as the picklist can have theoretically unlimited values, but the size limit field requires a value between 2 and 500 regardless of the actual count of items. Further, the use of a 0 or -1 to dismiss the size limit constraints is no longer an option.

To Reproduce
Steps to reproduce the behavior:

  1. Go to herb_rbge_9_3_23 on test panel >> url ending: specify/view/picklist/84
  2. Click on the + to add a value (should be greater than 500)
  3. Adjust size limit to 0/-1 and compare with a value between 2-500
  4. See error

Screenshots
Screenshot 2023-11-13 at 10 54 33 AM
Screenshot 2023-11-13 at 10 54 48 AM

Desktop:

  • OS: macOS
  • Browser: Chrome
  • Specify 7 Version: v7.9.1

Database Name: herb_rbge

Reported By
Robyn at RBGE

Additional context

Max's comment on a related issue:

It is set that way in the form definition:

<cell id="sizeLimit" initialize="max=500;min=2" isrequired="true" name="sizeLimit" type="field" uitype="spinner" />

Other than the form definition, there is no reason why it can't be -1. Specify 7 would handle both 0 and -1 as "no limit"

@bronwyncombs bronwyncombs added 1 - Bug Incorrect behavior of the product 2 - Forms Issues that are related to the form system labels Nov 13, 2023
@maxpatiiuk
Copy link
Member

thanks for providing lot's of details. just a FYI for the future: if an issue requires changing to default forms, add it to the "Form Changes" project. (assuming the workflow hasn't change since I left - @grantfitzsimmons can you confirm?)

The benefit of this is that when it comes to make a new sp6 release, we can easily see in a single place all the of pending form changes we need to make and can make them all at once.


aside: looks like most recent issues don't use projects anymore. @grantfitzsimmons was that an intentional change or just a slip up from lack of time/insufficient wiki documentation? there is significant value in assigning issues into back-end/front-end projects (for setting size&priority) as well as project for each component of specify for easily filtering and tracking (I use that all the time when searching for duplicates if I don't remember exact issue title)

@emenslin
Copy link
Collaborator

emenslin commented Jul 3, 2024

Can recreate as of edge (7.9.6)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - Bug Incorrect behavior of the product 2 - Forms Issues that are related to the form system
Projects
Status: Done
Development

No branches or pull requests

4 participants