-
Notifications
You must be signed in to change notification settings - Fork 492
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
6339 subjects disappear on edit #6356
Conversation
@sekmiller This still happens with Chrome:
|
Reviewed latest changes to the So there appears to be something going on with the EDIT vs CREATE versions of this form component. Also, on the metadataFragment, there is another version of the old scrolling |
Latest changes moved the selected values of the Hopefully it is possible to solve the inconsistency of this component between the edit and create workflows, by fixing the component's intended functionality, and not a custom code workaround. |
One question is have about the new component is if it allows authors to put the subjects in order. Can they make is so that "Physics" appears before "Chemistry"? The idea here is that the dataset is a little more about Physics than Chemistry. |
@pdurbin Nope. Alphabetical order. Is it worth trying to add ordering as an enhancement? |
@sekmiller nah. I'd sooner working on adding many, many more subjects before we prioritize the concept of "primary subject". Thanks. |
Here is the current broken UX as of the last commit to revert the AJAX changes from the component. CREATE WORKFLOW
EDIT WORKFLOW
|
(forgoing “Select…” when empty.)
We discussed in standup and I made the decision to move this as is. It is not perfect but it addresses a production bug. |
I would say the user experience for picking a language from a long list is much improved. Now there's search! 😄 |
New Contributors
Welcome! New contributors should at least glance at CONTRIBUTING.md, especially the section on pull requests where we encourage you to reach out to other developers before you start coding. Also, please note that we measure code coverage and prefer you write unit tests. Pull requests can still be reviewed without tests or completion of the checklist outlined below. Note that we use the "closes" syntax below to trigger Github's automation to close the corresponding issue once the pull request is merged.
Thanks for your contribution to Dataverse!
Related Issues
Pull Request Checklist