type-map-keeper

Centralize polymorphic dispatch by maintaining a single TYPES map on root classes and enforcing canonical map lookups at every materialization site. This prevents constant drift and brittle branching by establishing a single source of truth for subtype hydration.

A type map is a canonical lookup table that pairs TYPE_* constants with their target subtypes. You need a type map when handling polymorphic deserialization for object families like Channel or Interaction, ensuring inbound parts and outbound builders hydrate consistently.

To add a new subtype, define a new TYPE_* constant on the root class, register the entry in the root TYPES map, and verify all dispatch sites use the canonical map lookup to hydrate the correct subtype. This coordinated update ensures safe evolution.

Yes, DiscordPHP supports a single source of truth by centralizing TYPE_* constants on root families such as Channel, Interaction, Embed, and Component. Aligning inbound deserialization and outbound builder mappings to one map lookup stabilizes polymorphic dispatch.

Polymorphic dispatch breaks when TYPE_* constants and TYPES maps drift apart because materialization sites receive incorrect subtype mappings. Updating the canonical map lookup without aligning constants causes brittle branching and hydration failures across object families.

The best way to align inbound deserialization and outbound builder mappings is using a single canonical type map lookup at every materialization site. This enforces a single source of truth and prevents drift between how parts are hydrated and how builders are constructed.