Describe the bug
The PropertyCollector update closure passed to WaitForUpdatesEx is only triggered when a non-empty FilterSet occurs. This is an issue when side effects need to be triggered inside the update function such as notification mechanisms that an update was acknowledged.
It should be the choice of the update closure to determine whether to process the empty FilterSet or not.
To Reproduce
Steps to reproduce the behavior:
- Create a container view with no child entities such as an empty vm or host folder.
- Call wait for updates on the view.
- Observe that the update closure passed to WFU was not triggered even when an iteration of the WFU loop was processed.
Expected behavior
The onUpdatesFn should be triggered even if the FilterSet is empty.
Affected version
Since 95aa257.
Screenshots/Debug Output
N/A
Additional context
N/A
Describe the bug
The
PropertyCollectorupdate closure passed toWaitForUpdatesExis only triggered when a non-emptyFilterSetoccurs. This is an issue when side effects need to be triggered inside the update function such as notification mechanisms that an update was acknowledged.It should be the choice of the update closure to determine whether to process the empty
FilterSetor not.To Reproduce
Steps to reproduce the behavior:
Expected behavior
The
onUpdatesFnshould be triggered even if theFilterSetis empty.Affected version
Since 95aa257.
Screenshots/Debug Output
N/A
Additional context
N/A