Some issues with the plugin

[mtrfnvwork]

Incorrect works in some cases:

1. If two different folders have folders with the same name the plugin generates one class. For example, if I have assets/icons/my_folder and assets/images/my_folder the plugin will generate one class for the folder with "my_folder" name.
2. If I have a folder like assets/images/drawer/backgrounds and there is no another folders or assets inside assets/images/drawer folder, resulting class won't contain all parts of the path. It will be like Assets.images.backgrounds, without "drawer", so it's incorrect.

Also it's hard to migrate from v2. Give the opportunity to have strings instead of classes. I mean that expression like Assets.icons.user can return String, not Class. It can be configurable inside pubspec.yaml file.

And it will be great if you implement a configuration that disable generation of the methods to create Widgets like Image.asset or SvgPicture.asset. In come cases it don't need inside the project.

Many thanks!

[cr1992]

Thanks for the detailed report.

I’ve reproduced and fixed the main issues you mentioned:

• folder class conflicts when different asset roots contain directories with the same name
• missing intermediate directories in some robust path generation cases
• optional hierarchical String leaves via leaf_type: string to make migration easier

I also added regression tests to cover these cases.

The fixes are already in progress and will be included in the next update. Please give me a little time to finish verification and release it. I’ll push the update as soon as
possible.

Thanks again for the clear examples. They were very helpful.

[cr1992]

Incorrect works in some cases:

1. If two different folders have folders with the same name the plugin generates one class. For example, if I have assets/icons/my_folder and assets/images/my_folder the plugin will generate one class for the folder with "my_folder" name.
2. If I have a folder like assets/images/drawer/backgrounds and there is no another folders or assets inside assets/images/drawer folder, resulting class won't contain all parts of the path. It will be like Assets.images.backgrounds, without "drawer", so it's incorrect.

Also it's hard to migrate from v2. Give the opportunity to have strings instead of classes. I mean that expression like Assets.icons.user can return String, not Class. It can be configurable inside pubspec.yaml file.

And it will be great if you implement a configuration that disable generation of the methods to create Widgets like Image.asset or SvgPicture.asset. In come cases it don't need inside the project.

Many thanks!

This issue should be fixed in v3.2.0.

Please give the new release a try when you have a chance:
https://github.com/cr1992/FlutterAssetsGenerator/releases/tag/3.2.0

If you still see the same behavior, please reply here with a minimal repro or
your project layout, and I’ll investigate further.