iOS: add asyncnodeplugin resource path to bazel.build zip #300
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.
To fix publishing error for iOS
Change Type (required)
Indicate the type of change your pull request is:
patch
minor
major
Version
Published prerelease version:
0.7.0-next.5
Changelog
Release Notes
com.intuit.playerui
publishing scope (#253)Embracing the
player-ui
namespace, the base group ID, and correlating package scopes, have changed:com.intuit.player
->com.intuit.playerui
.jvm
from non-android artifactscom.intuit.player.jvm:core
com.intuit.playerui:core
com.intuit.player.android:player
com.intuit.playerui:android
com.intuit.player.plugins
com.intuit.player.jvm.plugins
com.intuit.player.android.plugins
com.intuit.playerui.plugins
Refactor existing DSL docs. (#288)
Update DSL docs
Remove Applitools (#277)
Enhance
AsyncViewStub.awaitView()
to ensure any childAsyncViewStub
s are resolved as well. This really only affects initial hydration, preventing weird isolated rendering jank by ensuring everything is ready to be shown on screen before actually rendering the top-level asset.🚀 Enhancement
com.intuit.playerui
publishing scope #253 (@sugarmanz)🐛 Bug Fix
📝 Documentation
Authors: 13