Fix default dropdown value #521
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If no default is specified in the field config, null was used instead of 0. For at least itemtype dropdowns, instead of showing the empty choice, it would show an empty dropdown. This seemed to be intentional in the core to be able to have no value selected at all, not even the empty choice.
See:
glpi-project/glpi#8682
Having a null value prevented the field from being sent when the form was submitted and would therefore bypass the mandatory field check.
Ref !23913 (Possibly. I noticed this issue while troubleshooting but their screenshot shows the empty choice being selected instead of an empty box).