Currently, when running node commands using the validator CLI (operator-cli <command> ...), any additional arguments provided after <command> are ignored without throwing an error. This behavior can be confusing for users as it does not alert them to incorrect usage or invalid commands effectively.
To improve usability and provide better feedback to users, this pull request aims to modify the validator CLI so that it throws an error when unrecognized arguments are passed after <command>. This change ensures that users are promptly informed about incorrect usage, helping them troubleshoot and correct their commands more efficiently.
Currently, when running node commands using the validator CLI (
operator-cli <command> ...), any additional arguments provided after<command>are ignored without throwing an error. This behavior can be confusing for users as it does not alert them to incorrect usage or invalid commands effectively.To improve usability and provide better feedback to users, this pull request aims to modify the validator CLI so that it throws an error when unrecognized arguments are passed after
<command>. This change ensures that users are promptly informed about incorrect usage, helping them troubleshoot and correct their commands more efficiently.