-
-
Notifications
You must be signed in to change notification settings - Fork 162
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
[BUG]: The path of assets is not correct #322
Comments
@jinaiyuanbaojie Thank you! |
@jinaiyuanbaojie |
This just broke svg images in my app... |
@noinskit |
From my perspective - yes, a bug. It worked for me before the change, stopped working after the change. |
Hi man, So you add the prefix packages/package_name by yourself before. Am I right? I am sure that the previous versions just returned the svg path as images/misc/food.svg style. |
I can't share the source directly, but what I'm doing is:
This is in the dependent package, in a class to be used by the top-level package. In 5.0.3 it's actually not possible to get the Note that |
Got it.
Could you try one of them? |
@jinaiyuanbaojie I'm not sure if I understand. There are workarounds, like downgrading to 5.0.2 or avoiding |
Yeah man. What matters is if it is a bug. |
@noinskit @jinaiyuanbaojie |
@noinskit @jinaiyuanbaojie When package_parameter_enabled = String get path => _assetName;
String get keyName => 'packages/$packageName/\$_assetName'; When package_parameter_enabled = String get path => _assetName;
String get keyName => _assetName; |
@wasabeef sure, this would work for me. |
|
@jinaiyuanbaojie @noinskit |
welcome. let's rock |
Is there an existing issue for this?
Version
No response
Command type
Dart command
What happened?
The plugin of svg, lottie, flare and rive generate the wrong path of the related assets.
I have raised a PR #321.
Not sure if it is a bug. If I am wrong, I think we can add a feature to show the correct path of assets under packages. :)
Relevant a pubspec.yaml.
No response
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: