-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Add svg to default copied bundle items for mac/ios #4863
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but @jonathanpeppers might need to confirm that these are the only locations the extensions are needed. I think they are because you got both targets files.
| /> | ||
| <ImageAsset | ||
| Include="$(iOSProjectFolder)**/*.xcassets/**/*.png;$(iOSProjectFolder)**/*.xcassets/*/*.jpg;$(iOSProjectFolder)**/*.xcassets/**/*.pdf;$(iOSProjectFolder)**/*.xcassets/**/*.json" | ||
| Include="$(iOSProjectFolder)**/*.xcassets/**/*.png;$(iOSProjectFolder)**/*.xcassets/*/*.jpg;$(iOSProjectFolder)**/*.xcassets/**/*.pdf;$(iOSProjectFolder)**/*.xcassets/**/*.svg;$(iOSProjectFolder)**/*.xcassets/**/*.json" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rolfbjarne I was looking at what is done in the iOS targets:
Should we actually be doing **\*.xcassets\**\*.* here instead and not listing file extensions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would make sense to not list the file extensions, and do the same as we do in iOS.
We did some testing, and it turned out you can put anything inside an *.xcassets directory (dotnet/macios@a0ad207).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't opened a ticket for this, but upon testing resources in main assemblies vs sub assembles it turns out iOS is overwriting main assembly resources with sub assembly resources. Android (correctly?) layers them together. So, if I have a drawable foo in sub assembly and bar in main assembly, the app sees both foo and bar. If I have the same in .xcassets then the app only sees foo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you open a new issue on that against the macios repo?
|
Can we rebase this, is this good to be merged @rolfbjarne ? |
|
@rmarinho I think Rolf is saying we should do something else instead of merging this: #4863 (comment) |
|
Ok so can we close this one for now? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this PR, I think we want to fix this, but since it seems iOS supports anything in the folder, could you update your PR to actually include *?
Include="$(iOSProjectFolder)**/*.xcassets/**/*.*"
| /> | ||
| <ImageAsset | ||
| Include="$(iOSProjectFolder)**/*.xcassets/**/*.png;$(iOSProjectFolder)**/*.xcassets/*/*.jpg;$(iOSProjectFolder)**/*.xcassets/**/*.pdf;$(iOSProjectFolder)**/*.xcassets/**/*.json" | ||
| Include="$(iOSProjectFolder)**/*.xcassets/**/*.png;$(iOSProjectFolder)**/*.xcassets/*/*.jpg;$(iOSProjectFolder)**/*.xcassets/**/*.pdf;$(iOSProjectFolder)**/*.xcassets/**/*.svg;$(iOSProjectFolder)**/*.xcassets/**/*.json" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you open a new issue on that against the macios repo?
|
I think we should close this and open a issue on macios repo |
|
They have done the work in the macos repo, we have to replicate in our platforms folder because we are adjusting the default paths. |
|
I think mobile is mixing up the comments, but this PR is just for the correct inclusions. The issue for macos is about resources overwriting things. |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
Description of Change
Implements #4862
Additions made
PR Checklist
Does this PR touch anything that might affect accessibility?
If any of the above checkboxes apply to your PR, then the PR will need to provide testing to demonstrate that accessibility still works.