-
Notifications
You must be signed in to change notification settings - Fork 7
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
[Doc] Add explanation of Svg
folders in README or SharedAssets.md
#262
Comments
@MartinZikmund this sounds like it has nothing to do with Resizetizer. By default Resizetizer doesn't do anything. The SDK does provide default includes. By default the SDK excludes adding UnoImage's in |
Ah, in that case I this will mainly be docs I guess (maybe I have missed this somewhere, but if not yet documented, that would be useful). And having such folder with a README in template could be nice as well, for out of the box clarity |
Svg
folders
@MartinZikmund he is the current doc https://platform.uno/docs/articles/features/svg.html?tabs=singleproject#how-to-use-svg And I agree with you @MartinZikmund, a default README (mentioning details about assets, resizetizer, svg,...) in the template would be helpful as right now we currently only have the SharedAssets.md with these details: |
Great that we have docs 👍 |
@jeromelaban, @MartinZikmund, @dansiegel |
Svg
foldersSvg
folders in README or SharedAssets.md
What would you like to be added:
The fact that folders named
Svg
are ignored by Resizetizer by default should be clearly mentioned in the default generated project as part of a README orSharedAssets.md
A guidance or even default folder in the template where.svg
would be ignored by Resizetizer.Reasoning behind this is that in WinUI .svgs are just content files by default. Currently .svgs in our case are resized by default, which is a discrepancy.Maybe it would make sense to include a folder likeAssets/Svg
in the project template with a README that says that .svg in that location is not resizedThe text was updated successfully, but these errors were encountered: