Problem
Currently, the interactive script does not clearly validate whether required dependencies
like arduino-cli, gum, and timer are properly installed and accessible in PATH.
If any dependency is missing or misconfigured, the script may fail silently or show
unclear error messages, making debugging difficult for users.
Expected Behavior
- The script should check for required dependencies at startup.
- If a dependency is missing, it should exit with a clear and user-friendly error message.
- When an internal
arduino-cli command fails, the full error output should be displayed.
Why This Matters
Clear dependency validation improves user experience and prevents confusion,
especially for first-time users setting up the tool.
I would like to work on improving dependency checks and structured error handling.
Problem
Currently, the interactive script does not clearly validate whether required dependencies
like
arduino-cli,gum, andtimerare properly installed and accessible in PATH.If any dependency is missing or misconfigured, the script may fail silently or show
unclear error messages, making debugging difficult for users.
Expected Behavior
arduino-clicommand fails, the full error output should be displayed.Why This Matters
Clear dependency validation improves user experience and prevents confusion,
especially for first-time users setting up the tool.
I would like to work on improving dependency checks and structured error handling.