Repository navigation
feat(ui): assemble libraries from shared object products - #93
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
export uiassembles UI libraries through the shared object-product pipeline. Each selected APK key produces aui.packmanifest with prefab roots, controllers, animation bindings, shaders and referenced fonts;index.jsonselects the corresponding products and embedded roots.The preview data retains serialized object identity and native component fields. Font traversal is selected per product so UI dependencies and localized story font products can coexist in a request.
Validation: synthetic UI and mixed-product assembly tests, schema checks, Ruff lint and formatting. Schemas and CLI documentation describe the product layout.