Include component icons as library assets #203
Merged
Conversation
This file contains 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
Arlodotexe
added
bug
|
Oh, wait this one is still broken and appears to be looking in the wrong place:
HeaderedContentControl doc... Miss this project maybe @Arlodotexe? |
michael-hawker
approved these changes
Aug 30, 2023
There was a problem hiding this comment.
@Arlodotexe looks good then, approving so you'll be all set once the Tooling PR merges to update the pointer here and get this merged.
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.
Needs CommunityToolkit/Tooling-Windows-Submodule#129
This PR consists of a tooling update that fixes an asset issue in the sample app.
Component icons and other
.pngfiles are now included as library assets instead of using the/SourceAssetsworkaround needed for this (now closed) issue: unoplatform/uno#2502.