Make use of general, any, list & map classes for configuration schema

Created on 22 March 2013, about 12 years ago
Updated 18 March 2025, 20 days ago

Motivation

#1866610: Introduce Kwalify-inspired schema format for configuration β†’ introduced the 'undefined', 'mapping' and 'sequence' types for configuration schemas. These are not in typed data. #1913328: Provide general list and map classes β†’ added the 'any', 'list' and 'map' types to typed data as a consequence. We should figure out how to use those to power the configuration schemas.

Proposed solution

Figure this out.

API changes

Might change the schema format if we want to be strict with the list/map types there.

πŸ“Œ Task
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

configuration system

Created by

πŸ‡­πŸ‡ΊHungary GΓ‘bor Hojtsy Hungary

Live updates comments and jobs are added and updated live.
  • D8MI

    (Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.

  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Thank you for creating this issue to improve Drupal.

    We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Production build 0.71.5 2024