If a user deletes an Entity Type or Bundle from their Drupal installation after a JSON API override configuration has been configured, the JsonApiResourceConfig entity associated with the type/bundle is not deleted as well. Besides not being hygienic, this can result in validation errors if a new entity or bundle with the same name is created at a later date.

CommentFileSizeAuthor
#2 jsonapi_extras_config_dependency-2903432-2.patch705 byteslogickal
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

logickal created an issue. See original summary.

logickal’s picture

logickal CreditAttribution: logickal at The Weather Company commented
Status: Active » Needs review
FileSize
jsonapi_extras_config_dependency-2903432-2.patch705 bytes

Here is a patch that adds the dependency between the original and jsonapi_extras config entities.

logickal’s picture

logickal CreditAttribution: logickal at The Weather Company commented

One outstanding question that I'm just now circling around to - what is the best way to clean up the side effects of this bug for those like me that were bitten by it? An update hook?

  • e0ipso committed 74efb5b on 8.x-1.x authored by logickal 
    fix(Dependencies): JsonApiResourceConfig entities are orphaned when...

e0ipso credited e0ipso.

e0ipso’s picture

e0ipso
Primary language Catalan
Location Can Picafort
CreditAttribution: e0ipso as a volunteer and at Lullabot commented
Status: Needs review » Fixed

Sorry it took so long to review/merge.

Many many thanks @logickal.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.