chore: removed extra navigation screen

[sohamkolhe9829]

What

• Removed extra onboarding screen.
• Upgraded intl package to intl^:0.19.0.

Screenshot

Fixes bug(s)

• Fixes: intl package version from intl^:0.18.1 to intl^:0.19.0.

Part of

• Remove irrelevant page on the onboarding? #5385

[monsieurtanuki]

Hi @sohamkolhe9829!
Please revert to intl:0.18.1 as we're still using flutter 3.19 (and it's incompatible).
Btw don't use the ^ syntax either.

[monsieurtanuki]

Hi @sohamkolhe9829!
Beyond the pubspec.yaml (that still isn't fixed), I assume that there should be deleted files and delete enum values in your PR, as we remove a page, and it's not the case...

[monsieurtanuki]

Probably because of the ^.

[g123k]

The disadvantage of 2 features in a single PR is when we only want a part of it.
To be honest, switching with intl to 0.19 will be OK once we release 4.15.0.
After that, we will probably switch to Flutter 3.22.

[monsieurtanuki]

@sohamkolhe9829 btw I would advise you to create and use branches and not to send PR from the main develop branch.

[sohamkolhe9829]

how to do that, can you help me out?

…

On Mon, 17 Jun 2024 at 11:40, monsieurtanuki ***@***.***> wrote: @sohamkolhe9829 <https://github.com/sohamkolhe9829> btw I would advise you to create and use branches and not to send PR from the main develop branch. — Reply to this email directly, view it on GitHub <#5391 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4E7ETHWG63MDQPQT2WSKPDZHZ4WNAVCNFSM6AAAAABJMVBZYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZSGM3DKMBZGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[monsieurtanuki]

how to do that, can you help me out?

I'm afraid not, I'm not very good with github. But you can find specific help about it on the web.

[g123k]

how to do that, can you help me out?

I'm afraid not, I'm not very good with github. But you can find specific help about it on the web.

That's not that hard.

1. Fork this repo:
   

2. Clone your fork

3. Create a new branch

4. Develop / commit / push on this branch

5. And back on GitHub, you will see a banner to create a Pull Request

[teolemon]

@sohamkolhe9829 I'm going to close, since @g123k had something that covers the same score. sorry for this one. Sorry for the mishap.