-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Optimize AVD to fix long vector paths Lint warning #785
Conversation
8559b92
to
6844a48
Compare
fb56403
to
61e519a
Compare
f47b976
to
8efa5fe
Compare
🔔 @alexvanyo (sorry for the ping, you were the last to update these files) |
Hi @SimonMarquis Could you please share how to reduce the 'long path' in the source file? I often struggle with reducing the length of SVG paths as it's not very intuitive. |
@lihenggui good question! I don't exactly remembered what I did back in June 🙈, but I think for these kind of AVD files, when you don't have access to the source SVG paths, I "simply" recreated an SVG file with the same paths and run them through SVGOMG and compress them until there was noticable changes at the expected zoom level and finally backported the compressed paths to the AVD files. Does that makes sense? |
Thank you! I will attempt to eliminate warnings in my projects. |
... with SVGOM, but you'll have to check on Android Studio the AVD diff. https://googlesamples.github.io/android-custom-lint-rules/checks/VectorPath.md.html
8972f3b
to
377d3be
Compare
... with SVGOM, but you'll have to check on Android Studio the AVD diff.
https://googlesamples.github.io/android-custom-lint-rules/checks/VectorPath.md.html