{"version":"2.1.265","anchor":"hook-lookup-api-reworked-from-map-lookups-to-accessor-method","canonical_anchor":"hook-lookup-api-reworked-from-map-lookups-to-accessor-method","heading":"Hook lookup API reworked from Map lookups to accessor methods","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/hook-lookup-api-reworked-from-map-lookups-to-accessor-method","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Hook lookup API reworked from Map lookups to accessor methods\n\nInternal hook lookups switched from raw map access to dedicated accessor methods\n\n**What**\n\nInternally, code that checks whether a hook applies (for example, hooks that run when a UI component renders) used to look values up directly in maps using `.has(...)` and `.get(...)`. It now goes through dedicated methods, `r.hooks(...)` and `r.matcherFor(...)`, instead.\n\n**Why**\n\nThis is an internal code cleanup with no expected effect on how hooks behave; it changes how the lookup is implemented, not what it returns.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}