Fix: Add null check for Select field options in fields_layout #407
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.
Changes:
and field.options
) in the condition to handle cases where options are empty or undefined for "Select" type fields.Why is this needed?
When I added a custom field of type Select without options, then code attempted to split
field.options
without checking if it existed, which could result in errors whenfield.options
isNone
or an empty string which resulted in error and not loading all the fields after that field. By adding this check, we ensure that the code only attempts to split the options whenfield.options
has a value.Code Changes: