Make TypedDataManager::createInstance() load data definition on its own

Created on 8 April 2015, over 10 years ago
Updated 9 May 2025, 4 months ago

The TypedDataManager::createInstance() method requires, beside the typed data definition name, the definition itself which basically means that instead of one line of code we need to write two/three.
If there is no significant reason for doing it this way I propose that the createInstance() method fetches the definition on its own.

Currently:

$field_name = 'field_item:something';
$definition = \Drupal::typedDataManager()->createDataDefinition($field_name);
$field_instance = \Drupal::typedDataManager()->createInstance($field_name, array('data_definition' => $definition));

Proposed change:

$field_instance = \Drupal::typedDataManager()->createInstance('field_item:something');
✨ Feature request
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

typed data system

Created by

Live updates comments and jobs are added and updated live.
  • 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 sharing your idea for improving Drupal.

    We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. 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.

    Thanks!

  • Status changed to Closed: outdated 14 days ago
  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Since there's been no follow up going to close this one out. If still a valid request can always re-open

    Thanks all

  • Now that this issue is closed, please review the contribution record.

    As a contributor, attribute any organization helped you, or if you volunteered your own time.

    Maintainers, please credit people who helped resolve this issue.

Production build 0.71.5 2024