Follow-up for #2843617: Field formatter mappings defined in getFieldFormatterMap have no effect.

We need to check that all field widet types from Drupal 6 & 7 are correctly mapped to Drupal 8 field widget types and that they are tested.

We may also consider cleaning the static maps and possibly move them to the field plugins getFieldWidgetMap() methods.

Drupal 6

Drupal 7

Was list_float the only thing missing from Drupal 7 'list'? Is Drupal 7 'list' type complete now?

Comments

maxocub created an issue. See original summary.

maxocub’s picture

maxocub commented
Issue summary: View changes
maxocub’s picture

maxocub commented
Status: Postponed » Active

Parent issue is fixed.

quietone’s picture

quietone commented
Title: Check that all field widget types are mapped and tested » [Meta] Check that all field widget types are mapped and tested
Issue summary: View changes

Let's make this a Meta to keep track of what has been completed and what is still to do.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Title: [Meta] Check that all field widget types are mapped and tested » [META] Check that all field widget types are mapped and tested
Category: Task » Plan

Thanks for pointing me to this issue!

quietone’s picture

quietone commented
Status: Active » Fixed

The reality is that we are not searching for field widget types that should be migrated. We have been re-actively adding them when someone files an issue and it is decided that a migration for the widget should be handled by core. This is all on a case by case basis.

As marvil07 said at the migrate meeting, "a responsive on-demand approach sounds like the more natural path forward"

Therefor closing this, 'fixed' seems the best status. Correct me if I am wrong.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.