LanguageFormatter is not used for nodes because it's still hard coded in NodeViewBuilder

Added test for the post_update.

Git was recognizing one file as binary when it generates the patch, by I found a workaround.

Fixed CS error.

Those dump files for update tests produce a lot of weird errors, hopefully I fixed all.

Maybe disabling the Spell check on some config imports.

Interdiff agains 83 because 84 didn't improve the issue.

+1 for me but will let someone else see what they think.

I tested manually the patch from #85.

Test #1
1. I used an empty Drupal 10.1.x
2. Applied the patch
3. Installed Drupal
4. Followed the patch from the IS

It worked as expected.

Test #2:
1. I used an empty Drupal 10.1.x
2. Installed Drupal
3. Followed the steps from IS
4. Applied the patch from the IS
5. Ran "drush updb".

It worked as expected, but I had to repeat the step 4: Check formatter option "Link to the Content", because it was unchecked after the update.

Let me know if I did something wrong.

Hi rpayanm,

That's the expected behavior after running the update, because it sets the formatter to match the hardcoded values to avoid unintended results on existing sites using that formatter.

Oh ok, thank you.

#2226493: Apply formatters and widgets to Node base fields → says it covered this, but looks like it didn't?

1. +++ b/core/modules/language/language.post_update.php
   @@ -13,3 +16,32 @@ function language_removed_post_updates() {
   +
   +/**
   + * Set language form display component as plain text and with label above.
   + */
   +function language_post_update_language_component_plain_text(&$sandbox = []) {
   +  $config_entity_updater = \Drupal::classResolver(ConfigEntityUpdater::class);
   +
   +  $callback = function (EntityViewDisplayInterface $view_display) {
   +    // Only update node view modes.
   +    if ($view_display->getTargetEntityTypeId() !== 'node') {
   +      return FALSE;
   +    }
   +    // Update language component if present.
   +    if ($view_display->getComponent('langcode')) {
   +      // Set label above as it was.
   +      $langcode['label'] = 'above';
   +      // Set to show it as plain text.
   +      $langcode['settings'] = [
   +        'link_to_entity' => FALSE,
   +        'native_language' => FALSE,
   +      ];
   +      $view_display->setComponent('langcode', $langcode);
   +      return TRUE;
   +    }
   +    return FALSE;
   +  };
   +
   +  $config_entity_updater->update($sandbox, 'entity_view_display', $callback);
   

   The logic here also needs to run in config entity presave so that it's applied to configuration shipped with modules and install profiles. Quite a lot of examples of this in 9.5 and 10.1, especially but not exclusively in views.

2. +++ b/core/modules/node/src/NodeViewBuilder.php
   @@ -41,16 +41,6 @@ public function buildComponents(array &$build, array $entities, array $displays,
    
   -      // Add Language field text element to node render array.
   -      if ($display->getComponent('langcode')) {
   -        $build[$id]['langcode'] = [
   -          '#type' => 'item',
   -          '#title' => t('Language'),
   -          '#markup' => $entity->language()->getName(),
   -          '#prefix' => '<div id="field-language-display">',
   -          '#suffix' => '</div>',
   -        ];
   -      }
        }
   

   Does the configured formatter end up in the same place in the render array?