Skip to content
This repository was archived by the owner on Feb 25, 2025. It is now read-only.

Conversation

@dnfield
Copy link
Contributor

@dnfield dnfield commented Nov 16, 2018

Fixes flutter/flutter#24420

This allows a consumer to decide whether they want to load the default storyboard/splash screen, and opt in by default. They could still get the previous behavior by calling [flutterViewController loadDefaultSplashScreen], but won't be forced into it in scenarios where they probably don't want it (as with a prewarmed engine for a child view/viewcontroller).

chinmaygarde
chinmaygarde approved these changes Nov 16, 2018
Copy link
Contributor

@jamesderlin jamesderlin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code looks fine to me. Switching to an opt-in system probably should be considered a breaking change, so be sure to announce it appropriately.

@dnfield dnfield merged commit c02dd8f into flutter:master Nov 16, 2018
@dnfield dnfield deleted the splash_flash_ios branch November 16, 2018 20:43
engine-flutter-autoroll added a commit to engine-flutter-autoroll/flutter that referenced this pull request Nov 16, 2018
engine-flutter-autoroll added a commit to flutter/flutter that referenced this pull request Nov 17, 2018
flutter/engine@5a694c4...c02dd8f

git log 5a694c4..c02dd8f --no-merges --oneline
c02dd8f Don't load a splash screen by default (flutter/engine#6883)
8a42213 Remove unused examples targets. (flutter/engine#6882)


The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants