mirror of
https://github.com/kubernetes/client-go.git
synced 2025-07-06 19:49:08 +00:00
client-go: call out WithContext inconsistency
This raises awareness so that developers hopefully get it right without having to learn about it from compile errors. It also explains that creating a PR to fix the naming is not desired. Kubernetes-commit: f40892f4813f29fc305d59073d2464a1fd7d6fe5
This commit is contained in:
parent
9638111dc7
commit
4e28a08da3
4
tools/cache/listwatch.go
vendored
4
tools/cache/listwatch.go
vendored
@ -154,6 +154,10 @@ type WatchFuncWithContext func(ctx context.Context, options metav1.ListOptions)
|
||||
// ListWithContextFunc and WatchFuncWithContext are preferred if
|
||||
// a context is available, otherwise ListFunc and WatchFunc.
|
||||
//
|
||||
// Beware of the inconsistent naming of the two WithContext methods.
|
||||
// This was unintentional, but fixing it now would force the ecosystem
|
||||
// to go through a breaking Go API change and was deemed not worth it.
|
||||
//
|
||||
// NewFilteredListWatchFromClient sets all of the functions to ensure that callers
|
||||
// which only know about ListFunc and WatchFunc continue to work.
|
||||
type ListWatch struct {
|
||||
|
Loading…
Reference in New Issue
Block a user