{"version":"2.1.251","anchor":"better-error-when-a-plugin-hook-gets-non-object-input","canonical_anchor":"better-error-when-a-plugin-hook-gets-non-object-input","heading":"Better error when a plugin hook gets non-object input","tier":"notice","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/better-error-when-a-plugin-hook-gets-non-object-input","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Better error when a plugin hook gets non-object input\n\nBad input to a plugin hook now produces an error naming the hooks involved.\n\n**What**\n\nHooks that plugins attach to interface calls now run through a shared chain runner that checks the event argument is an object first. When it is not, the error names the hooks involved instead of failing opaquely.\n\n**Evidence**\n\n`its input is no object, which the hooks on it`\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}