Conditional feature for map/unwind middleware #139
Merged
+153
−1
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.
This pull request enhances the middleware documentation by introducing conditional processing capabilities for both the
unwind
andmap
operations. It also provides detailed examples to demonstrate the use of these new features in practical scenarios.Enhancements to Middleware Configuration:
Unwind Operation:
condition
property to theunwind
configuration, allowing selective application of the unwind operation based on the properties of the incoming node.condition
property to unwind container statuses only when a specific action (e.g., "update") is detected in Kubernetes Pod events.Map Operation:
condition
property to themap
configuration, enabling conditional mapping based on the content of the incoming element.condition
property to route them to appropriate operations.These updates improve the flexibility and expressiveness of middleware configurations, making them more adaptable to complex, event-driven data workflows.