Convert config to content entities

Created on 20 November 2021, about 3 years ago
Updated 28 July 2023, over 1 year ago

Problem/Motivation

http_status_entity entity is a config entity and during export, an YML file is generated for each entity.

Proposed resolution

Convert config entity to content entity.

Remaining tasks

User interface changes

Change the entity ListBuilder

API changes

Extend ContentEntityBase instead ConfigEntityBase

Data model changes

✨ Feature request
Status

Needs review

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡¦Ukraine goodboy Kharkiv, Ukraine

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.

  • πŸ‡·πŸ‡ΊRussia sorlov

    we have some mess here with 2 MRs for single issue

    this should be fixed to have only 1 branch with proper changes

  • πŸ‡§πŸ‡΄Bolivia vacho Cochabamba

    mmm I got updated all locally(MR7 and MR8) however I can't use the MR7. @sorlov.

    Can you explain how you got this MR locally?

    The following, as usual, doesn't work:

    git remote add http_status_code-3250508 git@git.drupal.org:issue/http_status_code-3250508.git
    git fetch http_status_code-3250508
    git checkout -b '8.x-1.x' --track http_status_code-3250508/'8.x-1.x'
    fatal: A branch named '8.x-1.x' already exists.
    
  • Status changed to Needs review over 1 year ago
  • πŸ‡·πŸ‡ΊRussia sorlov

    Moved all changes from MR7 to MR8, so MR7 can be closed not (don't have enough permissions on my side to do that)

    so MR8 can be reviewed now

Production build 0.71.5 2024