Move non-ui Android RenderWorkflow concerns to workflow-runtime-android #1352
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.
Now that we have a
workflow-runtime-androidmodule (and published artifact), it is the place that makes sense to hold the Android versions ofrenderWorkflowIn, as they are beyond solely UI concerns, so do not need to be inworkflow-ui.Yes, I recognize that we could distribute this as an Android library from the
workflow-runtimeKMP module with a particular sourceset as well as particular publishing.I think that would be a good thing to do, but I don't want to figure out how to set that up right now. I think our balance of jvm, ios, and js artifacts from the KMP modules right now makes sense. I do not think we lose anything from this Android library being a standalone module (after all, it was before when it was in
workflow-ui).