Open jimjaeger opened 6 months ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
Describe the bug The example https://github.com/kubernetes-client/javascript/blob/master/examples/typescript/watch/watch-example.ts describes the following access "watchObj.metadata.resourceVersion". But in the implementation https://github.com/kubernetes-client/javascript/blob/master/src/watch.ts#L125 the watchObj has only object and type.
How about changing the example to watchObj.object.metadata.resourceVersion or change the call directly to object.metadata.resourceVersion?