{"version":"2.1.225","anchor":"new-bash-parse-rule-flags-two-statements-sharing-a-line","canonical_anchor":"new-bash-parse-rule-flags-two-statements-sharing-a-line","heading":"New bash-parse rule flags two statements sharing a line","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/new-bash-parse-rule-flags-two-statements-sharing-a-line","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### New bash-parse rule flags two statements sharing a line\n\nCommands cramming two statements onto one line are now flagged as too complex to auto-approve.\n\n**What**\n\nCommand analysis now treats a command as too complex when one statement directly follows another on the same line, since bash reads that as a single command.\n\n**Details**\n\n- Two node-type sets back the check: a statement-like set including `redirected_statement` and `ERROR`, and a smaller set of `negated_command`, `if_statement`, `while_statement` and `for_statement`\n- A new walk over the parse tree applies the rule and classifies the command accordingly\n\n**Evidence**\n\n`statement directly follows another statement on the same line`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}