⚠️ Functional Options Redux #536
Merged
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.
This switches over our functional options to actually be interfaced-based. Practically, this feels incredibly similar for users, to the point where I expect nobody will have to change their code (with the exception of Preconditions, which was a pointer).
The upsides are slightly more ergonomic options in some cases (like
client.MatchingLabels{"foo": "bar"}
instead of needingclient.MatchingLabels(map[string]string{"foo": "bar"})
, although the latter still works), as well as the removal of the need for separate variants for options that apply across different operations.Technically, this is a breaking change, since there are type signature changes.
Fixes #503 (see that issue for more details)