Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

FlutterGen Roadmap for v6 #384

Open
5 tasks
wasabeef opened this issue Apr 19, 2023 · 1 comment
Open
5 tasks

FlutterGen Roadmap for v6 #384

wasabeef opened this issue Apr 19, 2023 · 1 comment
Assignees
@wasabeef @AlexV525
Labels
contributions welcome Welcome contribute discussion Want to discuss it
Milestone
v6.0.0

Comments

@wasabeef
Copy link
Member

wasabeef commented Apr 19, 2023 •
edited

v6

Improvement

  • Split flutter_svg, lottie, rive, and flare integrations into separate packages.
  • Delete flare integration.
  • Allow the addition of custom integrations.
  • And more...

Team

  • Get more co-maintainers...
@wasabeef wasabeef added enhancement New feature or request and removed enhancement New feature or request labels Apr 19, 2023
@wasabeef wasabeef pinned this issue Apr 19, 2023
@wasabeef wasabeef self-assigned this Apr 19, 2023
@wasabeef wasabeef changed the title FlutterGen Roadmap for v6 v7 FlutterGen Roadmap for v6 Apr 19, 2023
@wasabeef wasabeef added this to the v6.0.0 milestone Apr 19, 2023
@wasabeef wasabeef added discussion Want to discuss it contributions welcome Welcome contribute labels Apr 19, 2023
@AlexV525 AlexV525 self-assigned this Sep 21, 2023
@bramp bramp mentioned this issue Oct 14, 2023
Merged
4 tasks
AlexV525 pushed a commit that referenced this issue Nov 14, 2023
@bramp
Refactored the AssetGenImage code to be another Integration (#432)
72fa49e 
## What does this change?

Refactored the `AssetGenImage` code to be another Integration, so that
it looks more similar to SVG/Lottie/Rive/etc.

This simplifies the assets_generator, and no longer forces
`AssetGenImage` to be output even when there are no images.

This can help ensure all integration are on level footing (perhaps
helping with task 1 in this list
#384)

## Type of change

- [x] Refactor to cleanup the code base.

## 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 unit:test`)
- [x] Ensure the analyzer and formatter pass (`melos run format` to
automatically apply formatting)
@tonyrbf96
Copy link

consider to add #391

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wasabeef wasabeef

@AlexV525 AlexV525

Labels
contributions welcome Welcome contribute discussion Want to discuss it
Projects
None yet
Milestone
v6.0.0
Development

No branches or pull requests
3 participants
@wasabeef @AlexV525 @tonyrbf96