It’s more of a theoretical problem, but when submitting the “Fields” form and somehow managing to circumvent the UI/Form API protection against changing a locked field type, we should catch that exception and display a warning instead.
(If nothing else, it will make PhpStorm happy – and is this not what programming is (recently) all about?)

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

drunken monkey created an issue. See original summary.

drunken monkey’s picture

Status: Active » Needs review
FileSize
1.2 KB

  • drunken monkey committed ce781c8 on 8.x-1.x
    Issue #3123173 by drunken monkey: Fixed uncaught exception when trying...
drunken monkey’s picture

Status: Needs review » Fixed

Committed.

Status: Fixed » Closed (fixed)

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