[Feature Request]: Have Parity with circtuitpython.org for board selection

[rcarteraz]

It appears there are a vast number of CP supported boards missing from the options when selecting a board with the extension. It would be ideal if the extension had parity with circuitpython.org for board selection.

[wmerkens]

Try this to update the boards in the ext (Done from Linux)

Use git and pull this repo and then go into the downloaded files, vscode-circuitpython/scripts

Then in the scripts directory, go and edit build-stubs.sh and at the bottom, rem out " rm -rf stubs/board" and run the script it will rebuild stubs/boards. then go replace it in .vscode/extensions/joedevivo.vscode-circuitpython-0.1.19-linux-x64/ the boards/stubs folders with the newly created one then this will go away.

Also, if the date in the path line in settings.json does not match the current bundle, you will get this problem, correct the date or erase .vscode and if you have a workplace file, erase it and let it all be rebuilt will, correct it for a bad date scenario

[rcarteraz]

Try this to update the boards in the ext (Done from Linux)

Use git and pull this repo and then go into the downloaded files, vscode-circuitpython/scripts

Then in the scripts directory, go and edit build-stubs.sh and at the bottom, rem out " rm -rf stubs/board" and run the script it will rebuild stubs/boards. then go replace it in .vscode/extensions/joedevivo.vscode-circuitpython-0.1.19-linux-x64/ the boards/stubs folders with the newly created one then this will go away.

Also, if the date in the path line in settings.json does not match the current bundle, you will get this problem, correct the date or erase .vscode and if you have a workplace file, erase it and let it all be rebuilt will, correct it for a bad date scenario

I’m not using Linux, will this work on macOS?

[wmerkens]

I am not sure since I am not on a Mac, but if you have Python installed and git installed and access to bash shell then possibly.

[danyeaw]

This does work with macOS as well, thanks for the hint @wmerkens!

One solution to this might be to do a monthly release of the extension so that it always has the latest boards.