Closed mgreenegit closed 3 years ago
I'm not sure what needs to be done for the build automation to correctly set the version? This could be included in the next 3.0 preview.
Merging #154 into master will decrease coverage by
1%
. The diff coverage is0%
.
@@ Coverage Diff @@
## master #154 +/- ##
=====================================
- Coverage 89% 88% -2%
=====================================
Files 5 5
Lines 575 583 +8
=====================================
Hits 517 517
- Misses 58 66 +8
I'm not sure what needs to be done for the build automation to correctly set the version? This could be included in the next 3.0 preview.
By adding 'breaking change' to the commit message/title when merging the PR. I will update the PR title so this is done. I will review during the weekend.
In testing this at length I found a more simple approach. Adding new commits. Will not require the additional function but I will add comments to explain why it is doing and why. This is still a breaking change because the expected input becomes a single string instead of a comma delimited array of strings.
This requires a much smaller change than I thought originally. Updating PR.
replaced by #155 155
Pull Request (PR) description
The intention of this PR is to support multiline settings. The correct format is for each entry to end with a null character and a new line.
Task list
This change is