-
-
Notifications
You must be signed in to change notification settings - Fork 393
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
Prevent duplicate entries in board_manager.additional_urls #1902
Conversation
Codecov ReportBase: 36.71% // Head: 36.68% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #1902 +/- ##
==========================================
- Coverage 36.71% 36.68% -0.04%
==========================================
Files 231 231
Lines 19723 19740 +17
==========================================
Hits 7242 7242
- Misses 11652 11669 +17
Partials 829 829
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
The tests that exercise the code paths ran during CI. Not sure why codecov report isn't showing coverage. Some bug in codecov? |
Hi @henrygab. Thanks so much for your pull request and also for your attention to code coverage! Unfortunately the Python-based integration tests are not considered in the coverage data. This data only describes the coverage provided by the Go-based unit tests like the ones you see here: https://github.com/arduino/arduino-cli/blob/master/arduino/builder/sketch_test.go If you are interested in this subject, there is additional information in this proposal for how we might eventually also determine the coverage provided by the integration tests: #1829 |
Thank you @henrygab! |
We are also migrating the python test into an equivalent version using golang test capabilities, you can find them inside the directory |
Fixes #1437.
Please check if the PR fulfills these requirements
before creating one)
our contributing guidelines
Docs have been added / updated (for bug fixes / features)UPGRADING.md
has been updated with a migration guide (for breaking changes)This change ensures that duplicate values are not introduced into configuration, such as for
board_manager.additional_urls
The following will result in two identical entries in the config:
Entries that accept multiple values are ensured to be unique. Care was taken to retain the order of entries. No error is generated due to duplicate entries (no error was previously generated ... this just prevents useless growth of this array).
titled accordingly?
This is not a breaking change.
Fixes #1437