Tags: FlutterGen/flutter_gen
Tags
🔖 5.8.0 (#582) ## 5.8.0 **Feature** - [#555](#555) Support build.yaml to configure. by [@b2nkuu](https://github.com/b2nkuu) - [#567](#567) Generate the `package` constant for generated font classes. by [@TesteurManiak](https://github.com/TesteurManiak) - [#569](#569) Enables `gaplessPlayback` by default for image assets. by [@AlexV525](https://github.com/AlexV525) - [#580](#580) Allows `mime: '>=1.0.0 <3.0.0'`. by [@AlexV525](https://github.com/AlexV525) **Development** - [#563](#563) Fix concurrency execution with melos. by [@wasabeef](https://github.com/wasabeef)
release: v5.7.0 (#561) ## 5.7.0 **Feature** - [#548](#548) Add Import abstraction for package imports alias. by [@AlexV525](https://github.com/AlexV525) **Development** - New releases [asdf-fluttergen](https://github.com/FlutterGen/asdf-fluttergen) and [setup-fluttergen](https://github.com/FlutterGen/setup-fluttergen). by [@ronnnnn](https://github.com/ronnnnn)
release: v5.6.0 (#534) ## 5.6.0 **Bug fix** - [#530](#530) Fix the Flavored assets. by [@AlexV525](https://github.com/AlexV525) - Please submit issues later if you have any feedback, this is blocking users from generating files if they are using flavors or transformations and there is no workaround for them. - [#532](#532) Provid the theme to SvgAssetLoader instead of SvgPicture. by [@Kirpal](https://github.com/Kirpal)
release: Release v5.5.0+1 (#517) ## What does this change? Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. Fixes #<issue_number_goes_here> 🎯 ## Type of change Please delete options that are not relevant. - [x] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [x] This change requires a documentation update ## Checklist: Before submitting your PR, there are a few things you can do to make sure it goes smoothly: - [ ] Make sure to open a GitHub issue as a bug/feature request before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests (`melos run test`) - [x] Ensure the analyzer and formatter pass (`melos run format` to automatically apply formatting) - [x] Appropriate docs were updated (if necessary)
PreviousNext