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
F22773455: D20741.diff
Mon, Oct 5, 9:45 PM
F22556874: D20741.id49454.diff
Wed, Sep 23, 4:58 PM
Unknown Object (File)
Aug 8 2026, 2:35 PM
Unknown Object (File)
Aug 7 2026, 12:12 PM
Unknown Object (File)
Aug 7 2026, 12:10 PM
Unknown Object (File)
Aug 7 2026, 6:37 AM
Unknown Object (File)
Jul 11 2026, 6:01 AM
Unknown Object (File)
Jul 7 2026, 6:52 AM
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.