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.

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

[FR]: Support deferred components #577

Open
2 tasks done
ianmaciel opened this issue Sep 17, 2024 · 1 comment · May be fixed by #576
Open
2 tasks done

[FR]: Support deferred components #577

ianmaciel opened this issue Sep 17, 2024 · 1 comment · May be fixed by #576
Labels
enhancement New feature or request

Comments

@ianmaciel
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Describe the problem

Deferred components allow developers to the app into multiple apk to reduce its size. This can be used to optimize the initial download and download components only on necessary but it is also mandatory for apk with more than 200MB.

This library initially looks for assets listed on flutter.assets of pubspec.yaml but does not include deferred components assets.

Without deferred components support, apps with more than 200 MB cannot use this library.

Describe the solution

Include the list of assets from every deferred compoment included on pubspec.yaml.

Additional context

Ideally this should create different classes to make clear for users in which compoment the assets is (must be load before usage). But to achive that an initial path level would be necessary even for the assets that does not use deferred compoments which would require significative changed and would generate incompatible assets.

Because of that I believe that as a first step, the library shouldn't cause any breaking changed because of deferred components, and users might be aware of deferred components by its path.

Code of Conduct

  • I agree to follow this project's Code of Conduct
@ianmaciel ianmaciel added the enhancement New feature or request label Sep 17, 2024
@ianmaciel
Copy link
Author

Note: As I had to implement the feature for my own usage, I didn't have the chance to open the issue and discuss the solution before.

I have already implemented a solution for this issue, which is available on #576

I tried to change as minimum as necessary to include the support and avoid breaking changes.

Feel free to propose changes if needed.

@ianmaciel ianmaciel linked a pull request Sep 17, 2024 that will close this issue
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant