Page MenuHomePhabricator

Fix incorrect construction of subtype map when validating "subtype" transactions against non-subtypable objects
ClosedPublic

Authored by epriestley on Aug 27 2019, 2:57 PM.
Tags
None
Referenced Files
F15353313: D20741.diff
Mon, Mar 10, 9:07 PM
F15332775: D20741.id.diff
Fri, Mar 7, 8:09 PM
F15332482: D20741.id49454.diff
Fri, Mar 7, 5:34 PM
F15331701: D20741.id49457.diff
Fri, Mar 7, 12:50 PM
F15282630: D20741.diff
Mar 4 2025, 12:50 AM
Unknown Object (File)
Feb 25 2025, 11:01 PM
Unknown Object (File)
Feb 25 2025, 10:39 PM
Unknown Object (File)
Feb 25 2025, 10:35 PM
Subscribers
None

Details

Summary

Fixes T13389. Currently, we try to "newSubtypeMap()" unconditionally, even if the underlying object does not support subtypes.

  • Only try to build a subtype map if subtype transactions are actually being applied.
  • When subtype transactions are applied to a non-subtypable object, fail more explicitly.
Test Plan

Clicked "Make Editable" in a fresh Calendar transaction form, got an editable form instead of a fatal from "newSubtypeMap()". (Calendar events are not currently subtypable.)

Diff Detail

Repository
rP Phabricator
Branch
subtype1
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 23312
Build 32030: Run Core Tests
Build 32029: arc lint + arc unit

Event Timeline

This revision was not accepted when it landed; it landed in state Needs Review.Aug 28 2019, 1:57 PM
This revision was automatically updated to reflect the committed changes.