SqlContentEntityStorage::getFieldStorageDefinitions() is poorly named and should not be public

Created on 9 October 2015, about 9 years ago
Updated 8 May 2024, 7 months ago

What are the steps required to reproduce the bug?

  1. Create a custom ContentEntityType.
  2. Attach at least one storage definition to this ContentEntityType using the hook 'entity_field_storage_info'.
  3. Create required database fields accordingly to the attached storage definition.
  4. Create an instance of that entity and try to save it.

What behavior were you expecting?

What happened instead?

Cause

Workaround

This is expected behavior. Storage Definitions in hook_field_storage_info do not go in the base tables and should throw the exception. Rename the confusing function and make it protected with appropriate deprecations and tests.

πŸ› Bug report
Status

Closed: duplicate

Version

8.8 ⚰️

Component
EntityΒ  β†’

Last updated about 6 hours ago

Created by

Live updates comments and jobs are added and updated live.
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.

Production build 0.71.5 2024