Plugin generates Assets class in the packages that included in projects

[mtrfnvwork]

FlutterAssetsGenerator v2 doesn't have this issue, but in v3 if you add some packages in pubspec.yaml, the plugin will change sources of these packages by adding Assets classes inside each package. But Assets class should be added inside current project only. Maybe It would be more preferable to generate Assets class only inside current project directory and add a way to customize/include/exclude (I don't know what will be more preferable) paths in case when project consists of multiple projects. I hope the problem is clear. Thanks!

[cr1992]

Thanks for the report. This has already been fixed and will be available in
the next release.

The issue was caused by overly broad module discovery in v3, which could make
the plugin generate Assets files for additional packages instead of keeping
generation scoped to the current project/module. That behavior has now been
corrected.

Please try again after the next version is published.

[cr1992]

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.

[yfming93]

the same issue had happed in v3.2.0.

[cr1992]

the same issue had happed in v3.2.0.

Could you share your project structure? Specifically:

1. Are you using path: dependencies in your pubspec.yaml?
2. Which packages are getting the unwanted Assets class generated?
3. Do those packages have a flutter_assets_generator: block in their pubspec.yaml?

A minimal repro or screenshot of the generated files would help narrow it down.