Skip to content

fix: use consistent error formatting across all commands #34

Description

@Rome-1

What

Some commands use `fmt.error()` for styled error output, while others use raw `console.error()`. Standardize on `fmt.error()` for consistency.

Why

Consistent error formatting means agents and scripts can reliably parse error output. Mixed formats make automation harder.

How to find them

```bash

Find raw console.error usage in commands (should use fmt instead)

grep -rn 'console.error' node/src/commands/
```

Fix

Replace `console.error(...)` with the project's `fmt.error(...)` utility, matching how other commands handle errors.

Files to check

  • `node/src/commands/backend/get.ts`
  • All files in `node/src/commands/` that use `console.error`
  • Python equivalents should also be checked for consistency

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions