Inline commenting breaks rule definition syntax

[bredler]

Adding a comment line to a rule directive definition like input, output , or params, breaks the syntax recognition.

The below example shows this as the error:
"SyntaxError: L50: Unrecognised keyword 'sam_1' in rule definitionSnakefmt(snakefmt:syntax-error)"

Removing the comment line "# MAPQ filtered files" resolves the error and creates a new error below the comment line "# FASTQ files"

[Hocnonsense]

Yes, but you can add four space before the #, and that can keep the comments:

rule:
    output:
        # comments
        a="some-file",
        # comments2
        b="other-files"