Add RemoveDefault()
extension method to fluent API for CMS webhook events
#15424
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.
Prerequisites
Description
PR #15345 added a fluent API for adding webhook events, but because the CMS adds a subset of events by default, you had to first clear all events to make sure you only end up with the configured ones. However, if other packages (like Deploy) also add events by default, those will also be cleared.
To address this, I've added a
RemoveDefault()
extension method, so the following example ensures all CMS default events are removed and only the content ones are added, without affecting other custom/non-CMS events: