{"version":"2.1.224","anchor":"sandbox-ignoreviolations-can-now-be-scoped-to-specific-comma","canonical_anchor":"sandbox-ignoreviolations-can-now-be-scoped-to-specific-comma","heading":"sandbox.ignoreViolations can now be scoped to specific commands","tier":"use","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/sandbox-ignoreviolations-can-now-be-scoped-to-specific-comma","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### sandbox.ignoreViolations can now be scoped to specific commands\n\nYou can silence sandbox violations for one command instead of all of them.\n\n**What**\n\nViolation suppression is no longer all-or-nothing. A `\"*\"` key still applies to every command, and other keys are matched against the command text so you can silence violations for one command only.\n\n**Details**\n\n- Recorded violations now carry the command, its encoded form and a timestamp.\n- The command text is recovered from a bounded cache of encoded commands, falling back to a decode that strips control characters.\n\n**Evidence**\n\n`ignoreViolations`\n\n- Area: Sandbox\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}