{"version":"2.1.275","anchor":"plugin-op-dispatch-ie-gains-a-post-processingscan-hook","canonical_anchor":"plugin-op-dispatch-ie-gains-a-post-processingscan-hook","heading":"Plugin op dispatch (ie) gains a post-processing\/scan hook","tier":"internal","area":"Plugin API","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/plugin-op-dispatch-ie-gains-a-post-processingscan-hook","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Plugin op dispatch (ie) gains a post-processing\/scan hook\n\nPlugin operation dispatch now runs every result through a new post-processing\/scan step before returning it\n\n**Unclear.** What the new scan\/post-processing step actually does to the op result is not stated in the finding.\n\n**What**\n\nThe internal dispatcher that routes plugin operations now passes a `scan` argument through, and every operation's result is run through a new post-processing step before it is returned to the caller, instead of being returned as-is.\n\n**Why**\n\nThe finding does not say what the post-processing step checks or changes, only that plugin operation results now pass through it before reaching whatever called them.\n\n- Area: Plugin API\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}