Skip to content

[BUG] NOOP accepts extra arguments instead of returning BAD #263

Description

@Aravinda-HWK

Steps to Reproduce

Send NOOP command with some arguments, it still behaves as a normal command.

Expected Behavior

RFC: NOOP takes no arguments; invalid arguments should return BAD.

Actual Behavior

Current dispatcher routes any NOOP tokenized command to the handler without checking argument count.
Current NOOP handler has no argument validation and always ends with OK

Relevant Logs / Screenshots

Impact: a command like A1 NOOP extra would likely return OK NOOP completed, where BAD is expected.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions