FOUR-13969: Allow user to decide what to do with the Screen Interstitial when importing assets#6134
Merged
ryancooley merged 5 commits intonextfrom Feb 1, 2024
Merged
Conversation
eiresendez
reviewed
Feb 1, 2024
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

0.0% Coverage on New Code
0.0% Duplication on New Code
Issue & Reproduction Steps
When following the guided template process, it has been noticed that the interstitial screen does show within the TemplateAssets check and it's been duplicated multiple times.
Interstitial screens should be part of the initial existing assets check, so the user can decide if they’ll be updated, replaced, or if a new version should be created
Solution
How to Test
Please ensure that the user has the option of what to do with the Interstitial Screen.
Please make sure that each selection works as expected. (Update | Keep Previous | Duplicate)
Related Tickets & Packages
ci:next
Code Review Checklist