Micon missing schema for its fields definitions

Interestingly enough, config inspector AND the tests both won't show any schema errors... interesting.

No idea, the schema definition seems to be fine on micon's site.

I tried redefining the storage definition using:

field.storage_settings.micon_string:
  type: mapping
  label: 'Micon string settings'
  mapping:
    max_length:
      type: integer
      label: 'Maximum length'
    case_sensitive:
      type: boolean
      label: 'Case sensitive'
    is_ascii:
      type: boolean
      label: 'Contains US ASCII characters only'

and "extending" it:

field.storage_settings.micon_string:
  type: field.storage_settings.string

similiar to https://git.drupalcode.org/project/entity_reference_revisions/-/blame/8....

Nothing seems to work and neither the tests nor the config inspector throws any schema errors before or after the changes.

@Grevil: Did you set up such a field like the one that shows the error in the tests?

My guess is, that this will first happen with a field set up?

Fixed, please review!

@Grevil: Nice! I left two minor comments.
But we shouldn't tag a release too soon with this change, I think. We need to be sure this has no side-effects.

Also one hard part is left I guess: Removing the old config from existing installations?
Perhaps you can find a snippet for that?

Alright all done! Added an update hook as well, and it runs well and as expected:

After the update, the field still works as expected and displays the given icon. Furthermore, no default_value is overriden or any other important field storage values.

Thanks @Grevil! LGTM! Still it's a heavy, but important change, so I'd like to have a sign-off by another maintaner who tested this.

RTBC from my side.
We should then wait with a new tagged release, once signed off and merged into dev, to see if this causes trouble somewhere.
Thank you!

@Anybody found another schema error:

content.field_symbol.settings.packages Undefined

Alright, should be fixed now, back to needs review.

I guess, @jacobbell84 is quite busy. I just ran into this issue again. As you RTBC'd this, I am just going to merge it. It was tested enough in my opinion.

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