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

Handling processInitialRoute for Initial Page Display in Patapata #32

Open
matsuyani556 opened this issue Dec 20, 2024 · 0 comments · May be fixed by #33
Open

Handling processInitialRoute for Initial Page Display in Patapata #32

matsuyani556 opened this issue Dec 20, 2024 · 0 comments · May be fixed by #33
Assignees
Labels
enhancement New feature or request

Comments

@matsuyani556
Copy link
Collaborator

Description

Currently, Patapata requires the processInitialRoute method to be called when displaying the first page. This is automatically invoked when using the StartupSequence. However, if StartupSequence is not used, the method must be called manually.

Until processInitialRoute is called, the first page in StandardMaterialApp.pages is displayed. However, this page does not handle DeepLink processing, resulting in pageData being null. This causes issues when pageData does not allow null values.

To address this:

  • Display a page created by SplashPageFactory until processInitialRoute is called.
  • Automatically execute processInitialRoute if StartupSequence is not used.

With this approach, the application’s initial page will properly handle DeepLink processing, ensuring a seamless user experience.

@matsuyani556 matsuyani556 added the enhancement New feature or request label Dec 20, 2024
@matsuyani556 matsuyani556 self-assigned this Dec 20, 2024
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