Missing schema

Thanks,
I do not understand the following:

-field.field_settings.languagefield:
+field.storage_settings.language_field:
 

Does that mean that the schema did not work at all?

and:

-  label: 'Custom language field settings'
+  label: 'Storage language field settings'
 

I guess the lae should be more like the field then the technical data.

It works but schema from module describes not existing data.
Module saves these settings as storage, in field.storage.*, not in field.field.* yaml files

We could ask if these settings should be stored in field.storage.* but this is separate history.

field.storage_settings.language_field is type defended in
https://git.drupalcode.org/project/drupal/-/blob/11.x/core/modules/field...

I could be wrong but I checked this this in "config-inspector" module.
It is very likely more formattes/widgets require interventions too.
Please feel free to make changes in MR

I applied your patch.
in config-inspector I still see errors. moving the language_range type from string to integer lowers the number of mistakes (errors?) from 7 to 1.
I see you do an array_keys to solve the problem. However, key 11 does not fit.
I checked https://www.drupal.org/docs/drupal-apis/configuration-api/configuration-... →

I was wondering why only 1 value gave an error. The last patch fixes that.
Not sure why the following must be an integer, as keys are both integer and string, and documentation seems to state that it does not matter:

    language_range:
      type: sequence
      label: 'Enabled language ranges'
      sequence:
        type: integer
        label: 'Language range'

Please test you import/export with a numeric and a string key (e.g., 'All predefined languages' and 'site default language').

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

@alorenc,
this change causes that Languagefield cannot be added as a new field anymore.
Please check 🐛 TypeError when adding the field (only on 1.9+dev version) Active

change from #9 is now undone, due to severe side effect as per 🐛 TypeError when adding the field (only on 1.9+dev version) Active .

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