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

Migrating to flutter 2.0 #27

Open
shagun25 opened this issue Mar 14, 2021 · 7 comments
Open

Migrating to flutter 2.0 #27

shagun25 opened this issue Mar 14, 2021 · 7 comments
Assignees
Labels
gssoc21 hard Level3 New features, major bug fixing.

Comments

@shagun25
Copy link
Owner

shagun25 commented Mar 14, 2021

Feature: Project migration to flutter 2.0

Expected Behaviour: All packages should be compatible with flutter 2.0, deprecated field should be replaced with a new one.
POINTS-25

@shagun25 shagun25 added gssoc21 hard Level3 New features, major bug fixing. labels Mar 14, 2021
@pawan2806
Copy link
Contributor

Hi ,Can I work on this ? I am participating in GSSOC21.

@hiashutoshsingh
Copy link
Collaborator

@pawan2806 How you will be implementing this? Please let us know your approach.

@shagun25
Copy link
Owner Author

Hi ,Can I work on this ? I am participating in GSSOC21.

Are you working ?

@pawan2806
Copy link
Contributor

Hi ,Can I work on this ? I am participating in GSSOC21.

Are you working ?

I might need some help with this. Many of the packages don't support null safety yet. And as almost all the packages depend on each other, the project is giving countless errors on increasing the dependency versions of packages that actually support null safety.

Screenshot (579)
Screenshot (580)

@shagun25

@hiashutoshsingh
Copy link
Collaborator

Hi ,Can I work on this ? I am participating in GSSOC21.

Are you working ?

I might need some help with this. Many of the packages don't support null safety yet. And as almost all the packages depend on each other, the project is giving countless errors on increasing the dependency versions of packages that actually support null safety.

Screenshot (579)
Screenshot (580)

@shagun25

Hey @pawan2806 ,
If some packages are not having their null safety then we can follow two approaches:

  1. update packages to the null safety beta version(remaining on previous flutter stable version 1.22.0-1.22.6)
  2. Migrating project to flutter 2.0 and those packages whose dependencies are on others we can write them in dependency-overrides https://dart.dev/tools/pub/dependencies#dependency-overrides

@pawan2806
Copy link
Contributor

Hi ,Can I work on this ? I am participating in GSSOC21.

Are you working ?

I might need some help with this. Many of the packages don't support null safety yet. And as almost all the packages depend on each other, the project is giving countless errors on increasing the dependency versions of packages that actually support null safety.
Screenshot (579)
Screenshot (580)
@shagun25

Hey @pawan2806 ,
If some packages are not having their null safety then we can follow two approaches:

  1. update packages to the null safety beta version(remaining on previous flutter stable version 1.22.0-1.22.6)
  2. Migrating project to flutter 2.0 and those packages whose dependencies are on others we can write them in dependency-overrides https://dart.dev/tools/pub/dependencies#dependency-overrides

Screenshot (592)

@hiashutoshsingh I think we have to wait until all packages are updated to null-safety versions.

@hiashutoshsingh
Copy link
Collaborator

hiashutoshsingh commented Mar 26, 2021

is dependency override not working here. I guess it should. @pawan2806

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gssoc21 hard Level3 New features, major bug fixing.
Projects
None yet
Development

No branches or pull requests

3 participants