{"version":"2.1.229","anchor":"bash-commands-that-are-not-strings-no-longer-reach-the-parse","canonical_anchor":"bash-commands-that-are-not-strings-no-longer-reach-the-parse","heading":"Bash commands that are not strings no longer reach the parser","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/bash-commands-that-are-not-strings-no-longer-reach-the-parse","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Bash commands that are not strings no longer reach the parser\n\nA non-string Bash command can no longer reach the command parser.\n\n**What**\n\nThe check deciding whether a Bash invocation is a read or search command bailed out only on falsy values, so a non-string command could be passed to the parser. It now bails out on anything that is not a string.\n\n**Evidence**\n\n`isSearchOrReadCommand`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}