Conversation
Signed-off-by: Brian Witt <brianwitt@gmail.com>
Ensure deterministic output
added info about default resource catalog in README
Rework resource generation
…-resources #885 fix usage of LocalSystemTheme on compose 1.12+
added paparazzi test case
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.
Changes
Rework resource generation #881
MethodTooLargeExceptionin projects with large resource catalogs (#632).GenerateMultiplatformResourcesTaskand resource change detection (#810).watchosDeviceArm64target support (#870).Ensure deterministic output #883 made generated resources reproducible across machines by sorting filesystem-derived inputs and using stable hashes (#882).
Fix Compose Multiplatform 1.12 resource rendering #888 fixed
painterResource()crashes on iOS caused by theLocalSystemThemeAPI change (#885).Breaking changes
Resource accessors are now generated as top-level extension properties.
Resource access expressions remain unchanged, but code outside the generated resources package must import each resource accessor.
Before:
After:
Alternatively, all generated accessors can be imported at once:
Replace com.example.resources with the package configured in resourcesPackage.
Thanks
@bwitt