-
-
Notifications
You must be signed in to change notification settings - Fork 431
Boards Manager does not have "Online help" links #1781
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
Comments
This is the same behavior as Arduino IDE 1.x. The "More info" link is defined by the package index's Arduino IDE 1.x has a separate "Online help" link, defined by It looks like the gRPC interface's |
Thanks for the update. As I was reading again the issue, I just realized I was on the board manager and not the library manager. So most of my comments about library info were a bit misguided, as they should point to the board family information. As a side note, I just checked the library manager links and the link to "More info" leads to the proper library information. |
The work on the Arduino CLI side has now been completed arduino/arduino-cli#2009 (Thanks Matteo). I have transferred the issue back to the Arduino IDE repository and reopened it because additional work is needed in the Arduino IDE codebase in order to add the link to the Boards Manager view. |
As I was reviewing the new Arduino IDE 2.0.0-beta.3, I was trying to install the supporting library for Arduino Nano 33 BLE Sense.
I opened the Boards Manager from the tool menu and looked for the board. Looking for additional information to see if I should install Arduino mbed-enabled board or Arduino nRF52 board package, I discovered that all the links for "More info" on Arduino boards are pointing to the front page of the Arduino website, instead of the library information. This makes the "More info" button for libraries quite useless.
P.D If you look for Sense, or Arduino Nano 33 BLE Sense in board manager nothing appears in the search results. This might be a separate bug too.
The text was updated successfully, but these errors were encountered: