Add unit tests for maskApiKey edge cases

[404-Page-Found]

Description

The maskApiKey function in src/commands/config.ts masks stored API keys for display. It has a visibleLength calculation (Math.min(4, Math.max(2, apiKey.length))) that handles short and long keys differently, but no unit tests exercise this function directly.

Proposed Solution

Tests should cover:

• undefined returns 'not stored in config'
• Empty string returns 'not stored in config'
• A 1-character key returns 2 visible characters (due to Math.max(2, ...))
• A 2-character key returns the full key + dots
• A 3-character key returns the full key + dots
• A 4+ character key shows first 4 characters + dots

Why It is a Good First Issue

Pure function with clear edge cases. The test file tests/config-command.test.mjs already imports from dist/commands/config.js and has the test infrastructure.

Files

• src/commands/config.ts (lines 10-17)
• tests/config-command.test.mjs

[shekar50]

Hi @404-Page-Found,

I'd like to work on this issue. I'll add coverage for the listed edge cases in tests/config-command.test.mjs and verify the existing test suite still passes.

Thanks!

[shekar50]

Hi @404-Page-Found,

I've opened PR #164 to add edge-case coverage for maskApiKey.

The PR includes tests for:

• undefined
• empty string
• 1-character key
• 2-character key
• 3-character key
• 4-character key
• long keys

Verified locally with:

• npm run build
• node --test tests/config-command.test.mjs

Thanks!

[404-Page-Found]

Thanks for opening this issue! The edge cases for maskApiKey are well-identified — the Math.max(2, ...) behavior on short keys and the 4-character threshold for display are exactly the kind of logic that benefits from direct test coverage. The existing test file at tests/config-command.test.mjs already has the infrastructure in place, so this should be a straightforward addition. Nice breakdown of the expected outputs for each key length.