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

[Feature] Configurable Dropdown object limit for forms #3277

Closed
ALonelyJuicebox opened this issue Dec 14, 2022 · 1 comment · Fixed by #3459
Closed

[Feature] Configurable Dropdown object limit for forms #3277

ALonelyJuicebox opened this issue Dec 14, 2022 · 1 comment · Fixed by #3459
Labels
bounty This issue has a bounty on it in the OpenCollective feature request

Comments

@ALonelyJuicebox
Copy link

Challenge:
In a valid effort to improve performance, a 200 object limiter was placed on all dropdown forms in the 0.18 release.
To the credit of the devs, this absolutely makes sense for the Studios and Performers dropdown forms. Lots of performers and studios out there, and users aren't often going to be hunting through those forms to find a studio/performer.

Things are different when it comes to Tags though.
The 200 object limit is just a little bit too restrictive.

When it comes to Tags, I am constantly scrolling through that dropdown form and ensuring a video has been tagged with all the appropriate tags for that media. Based on comments on the Discord, I'm not alone in this thinking either.

Proposed Solution:
Add a configurable option under Settings > Interface > Editing to define the max object size of the dropdown.

Proposed UX:
dropdownsettings

@WithoutPants WithoutPants added the bounty This issue has a bounty on it in the OpenCollective label Feb 20, 2023
@WithoutPants
Copy link
Collaborator

$50 bounty placed (contribution no. 626966)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bounty This issue has a bounty on it in the OpenCollective feature request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants