Don't hardcode the base table name in file.module

Created on 9 January 2017, over 7 years ago
Updated 23 May 2023, about 1 year ago

Problem/Motivation

I want to extend the \Drupal\file\Entity\File entity by using other base table but still reuse most of the code from file.module. Unfortunately in many places the 'file' entity base table {file_managed} is hardcoded, making hard to extend the entity.

Proposed resolution

Remove the table name hardcoding where possible. For example in tests it's OK to use the hardcoded value as the tests are run with the core 'file' entity.

Remaining tasks

None.

User interface changes

None.

API changes

None.

Data model changes

None.

πŸ“Œ Task
Status

Closed: won't fix

Version

11.0 πŸ”₯

Component
File moduleΒ  β†’

Last updated 3 days ago

Created by

πŸ‡·πŸ‡΄Romania claudiu.cristea Arad πŸ‡·πŸ‡΄

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.

  • πŸ‡ΊπŸ‡ΈUnited States Kristen Pol Santa Cruz, CA, USA

    As part of the Bug Smash Initiative, we are triaging issues that are marked "Postponed (maintainer needs more info)". This issue was marked "Postponed (maintainer needs more info)" almost two years ago.

    Since there was no additional information provided since it was requested last year, I'm marking the issue "Closed (won't fix)". If anyone can provide the additional required, update the issue summary and set the issue status back to "Active" [or "Needs Work" if it has a patch, etc.].

    Thanks!

Production build 0.69.0 2024