Open bramp opened 11 months ago
When migrating Image.asset(...) to Assets.images I wanted to ensure all current and future uses were migrated. To avoid regressions, and ensure all contributors to the code base used the same style.
Image.asset(...)
Assets.images
Having a lint rule would be useful, as such I created one at https://pub.dev/packages/flutter_gen_linter
In your `pubspec.yaml`` add:
dev_dependencies: custom_lint: ^0.5.0 flutter_gen_linter: ^1.0.0
and create a analysis_options.yaml and add:
analyzer: plugins: - custom_lint
Happy for https://pub.dev/packages/flutter_gen_linter to fold into this main project. This was my first Dart Package so I in part wrote it to learn.
@bramp Still interested in this? I'd be happy to see if this shipped along with our libraries.
Is there an existing issue for this?
Describe the problem
When migrating
Image.asset(...)
toAssets.images
I wanted to ensure all current and future uses were migrated. To avoid regressions, and ensure all contributors to the code base used the same style.Describe the solution
Having a lint rule would be useful, as such I created one at https://pub.dev/packages/flutter_gen_linter
In your `pubspec.yaml`` add:
and create a analysis_options.yaml and add:
Additional context
Happy for https://pub.dev/packages/flutter_gen_linter to fold into this main project. This was my first Dart Package so I in part wrote it to learn.
Code of Conduct