Update ProtectionChanges to contain the remaining possible return values#2486
Update ProtectionChanges to contain the remaining possible return values#2486gmlewis merged 4 commits intogoogle:masterfrom eolso:update-branch-protection-changes
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Codecov Report
@@ Coverage Diff @@
## master #2486 +/- ##
=======================================
Coverage 98.03% 98.03%
=======================================
Files 122 122
Lines 10705 10705
=======================================
Hits 10495 10495
Misses 144 144
Partials 66 66
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
|
Fixed! @gmlewis the structs for the fields |
Thank you, @eolso - I'll review this after work. Meanwhile, yes, I prefer to avoid breaking API changes if possible... and in this case I think it is probably fine to have the slight inconsistencies... so maybe reverting these two name changes would be preferable. If any other contributors have other opinions, I'm happy to discuss it. |
|
Agreed, "consistency" can wait. Reverted breaking changes 😄 |
Fixes issue #2485. The
Fromvalues only seem to come in the variants ofstring,boolor[]string, so it's possible these objects could be consolidated into something more generic maybe.e.g.
This went against the current pattern so I made everything a
<Value>Changesstruct instead :D