chore: use correct field separator in keywords.txt#96
chore: use correct field separator in keywords.txt#96faustbrian merged 2 commits intoArkEcosystemArchive:developfrom per1234:keywords-separator
Conversation
The Arduino IDE requires the use of a single true tab separator between the keyword name and identifier. When spaces are used rather than a true tab, the keyword is not highlighted. Reference: https://github.com/arduino/Arduino/wiki/Arduino-IDE-1.5:-Library-specification#keywords
|
Thanks for submitting this pull request! A maintainer will review this in the next few days and explicitly select labels so you know what's going on. If no reviewer appears after a week, a reminder will be sent out. |
|
Thank you, @per1234 This looks good to go, @faustbrian |
|
A contributor has approved this PR. A maintainer will merge this PR shortly. If it shouldn't be merged yet, please leave a comment saying so and we'll wait. Thank you for your contribution! |
|
The ci/circleci: build-linux-gcc7 job is failing as of e024576f603fc8eac3b4ae6167a8dece8dd43fdc. Please review the logs for more information. Once you've pushed the fixes, the build will automatically re-run. Thanks! |
1 similar comment
|
The ci/circleci: build-linux-gcc7 job is failing as of e024576f603fc8eac3b4ae6167a8dece8dd43fdc. Please review the logs for more information. Once you've pushed the fixes, the build will automatically re-run. Thanks! |
|
Your pull request has been merged and marked as tier 5. It will earn you $5 USD. |
|
@per1234 Can you provide me with your ARK address for GitHub bounty? You can also contact me on ARK's Slack - https://ark.io/slack (username : boldninja) and direct message me your address there. |
|
Here it is: Thanks! |
The Arduino IDE requires the use of a single true tab separator between the keyword name and identifier. When spaces are used rather than a true tab, the keyword is not highlighted.
Reference:
https://github.com/arduino/Arduino/wiki/Arduino-IDE-1.5:-Library-specification#keywords
What kind of change does this PR introduce?
Does this PR introduce a breaking change?
Does this PR release a new version?
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
developbranch, not themasterbranchIf adding a new feature, the PR's description includes: