Move exceptions in \Drupal\Core\Entity\EntityDisplayBase::__construct to assertions

Created on 29 July 2015, almost 9 years ago
Updated 17 August 2023, 11 months ago

Problem/Motivation

There is no reason the 4 exceptions in EntityDisplayBase have to be exceptions, they could be assertions as well

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

πŸ“Œ Task
Status

Closed: outdated

Version

9.5

Component
EntityΒ  β†’

Last updated about 8 hours ago

Created by

πŸ‡©πŸ‡ͺGermany dawehner

Live updates comments and jobs are added and updated live.
  • Runtime assertion

    It deals with the addition of an assert() statement(s) to the code, and/or contains a test patch where one is failing indicating a need to change code or the documentation the statement was based on.

  • Needs subsystem maintainer review

    It is used to alert the maintainer(s) of a particular core subsystem that an issue significantly impacts their subsystem, and their signoff is needed (see the governance policy draft for more information). Also, if you use this tag, make sure the issue component is set to the correct subsystem. If an issue significantly impacts more than one subsystem, use needs framework manager review instead.

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

    Since there hasn't been a follow up or activity in 8+ years going to close for now.

    If still valid please reopen, maybe updating issue summary.

    Thanks all

Production build 0.69.0 2024