Better esp platform names #122
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding platform names for
feather_esp8266andfeather_esp32which aliasesp8266andesp32Why? Scripts which resource the platform name (
.arduino-platform), i.e:${{ matrix.arduino-platform }}., will generate files such aswippersnapper.esp32.littlefs....bin. These files do not contain the platform name, only the board name.I'm adding these as duplicates since we use the
esp8266/esp32platforms across a large # of libraries and this will be non-breaking (and mostly used for wippersnapper)