Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
By jibran on
Change record status:
Published (View all published change records)
Project:
Introduced in branch:
8.0.x
Introduced in version:
8.0.0-beta10
Issue links:
Description:
Prior to 8.0.0-beta10, OptionsWidgetBase::getOptions() determined the presence of an "empty / no selection" option based on a hardcoded list of widget plugin IDs (the known core widgets extending that base class). Therefore, custom or contrib widgets extending OptionWidgetBase were not able to display an empty option without completely overriding OptionsWidgetBase::getOptions().
In 8.0.0-beta10, this hardcoded logic in OptionsWidgetBase::getOptions() has been replaced by a call to a new OptionsWidgetBase::getEmptyLabel() method, which provides a simpler override point for subclasses.
See OptionsWidgetBase::getEmptyLabel() for more details.
During the re-factoring of the code,
- the following constants have been removed :
OptionsWidgetBase::OPTIONS_EMPTY_NONE
OptionsWidgetBase::OPTIONS_EMPTY_SELECT
- OptionsWidgetBase::getEmptyOption() was also removed, and replaced by getEmptyLabel()
Impacts:
Module developers
