Why do we use client.WatchAsync<TEntity>() rather than client.Watch<TEntity>() for the entity watcher? #795

Unanswered

slacki123 asked this question in Q&A

slacki123
Jul 30, 2024

Hi, just wondering why do we use the WatchAsync<TEntity>() instead of the Watch<TEntity>() method to watch for custom resources here
https://github.com/buehler/dotnet-operator-sdk/blob/main/src/KubeOps.Operator/Watcher/ResourceWatcher%7BTEntity%7D.cs#L139

I recently implemented some of my own watchers with the Watch() method and it works really well with simple implementation. What's the reasoning for using WatchAsync<TEntity>()? Is it because Watch<TEntity>() wasn't available when the operator was first written or is it lacking some functionality?

Replies: 1 comment

buehler
Aug 5, 2024
Maintainer

The reason is simply that when I rewrote v8, I used async enumerables and other modern language features. There is no particular reason.

0 replies

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment