-
-
Notifications
You must be signed in to change notification settings - Fork 408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make error message from compiling w/o board selected more user friendly #62
Comments
@per1234 |
@giannicolab @Francesco-Stasi @Alberto-Iannaccone |
with an upcoming minor UX facelift the Verify/Upload buttons won't be enabled unless they can yield results.
Those changes are not exactly around the corner, so maybe it's worth to just map this error to a more meaningful string for now. |
Related upstream: arduino/arduino-cli#1762 |
Currently blocked by this: arduino/arduino-cli#1812. The CLI is used to log |
Related: #845 |
Describe the current behavior
On the first use, no board is selected. A new user may not realize it is necessary to select one. If they attempt to compile a sketch without selecting one, they will receive only this cryptic error message:
and this notification:
This doesn't mean anything to even very advanced IDE users, and the user will have difficulty understanding what they need to do to resolve it.
To reproduce
The board/port selector menu should show "❌ No board selected".
Describe the request
Show a user friendly error message. Something like:
Desktop
Date: 2022-01-24T16:22:30.529Z
CLI Version: 0.20.2 [13783819]
Additional context
Even among Arduino CLI users, I have found that the concept of "FQBN" is not widely known. IDE users are even less likely to be familiar with this acronym, and even less anxious to spend their time learning what it means, since the it is not otherwise a part of the IDE user experience.
Note that the error message produced by the reproduction instructions above is currently different than described due to a recent regression in Arduino CLI: arduino/arduino-cli#1812
Related
The text was updated successfully, but these errors were encountered: