Adding APIs for finer control over a WorkflowHost's renderings #384
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 PR adds a
managedRenderings
property to WorkflowHost, behind aWorkflowHostManagement
SPI. When this property is enabled,shouldSkipRenderForOutput(_:)
returns true so that the host's workflow isn't rendered. A newmanagedUpdate(workflow:)
API can be used to perform the actual rendering.The planned use case for this API is when a container attaches one or more
WorkflowHost
instances to a workflow tree, bridging the host's renderings and output into the main tree and rerendering the host when the main tree renders. Without this API, the attached host's workflow will render an extra time when actions are applied: once when the action is applied and once when the main tree renders. This API allows the container to render the hosted workflow only after the main tree renders.Checklist