[BUG]: Wrong output assets path with integrations.

[wasabeef]

Is there an existing issue for this?

• I have searched the existing issues

Version

5.0.3

Command type

build_runner (Default)

What happened?

This just broke svg images in my app... path that was previously correctly packages/package_name/images/misc/foo.svg after upgrade became packages/package_name/packages/package_name/images/misc/foo.svg which obviously doesn't work. What am I doing wrong? In any case, 5.0.3 was definitely not a backward-compatible update.

#322 (comment)

Relevant a pubspec.yaml.

No response

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[noinskit]

Friendly ping?

I've got nothing against exposing the full path including the package in generated classes. In fact, AssetGenImage has been doing that for a long time (path vs keyName).

What's making me nervous is changing the semantics of public fields in a minor version update without a warning, and doing this with naming inconsistent between different autogenerated classes (SvgGenImage vs AssetGenImage).

[wasabeef]

@noinskit
I just released v5.1.0.