This repository has been archived by the owner on May 13, 2024. It is now read-only.
✨New welcome flow for importing settings from other browsers #504
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.
Issue tracker: brave/brave-browser#1530
Spec: brave/brave-core#2679 (comment)
Changes
Select
into "features/welcome" since we have multiple "screens" in welcome relying on it - it didn't make sense to have all of them cross-referencing a shields component (I am assuming we can lift it to a general directory when we migrate our stories to core)Test plan
brave://welcome
should still load properly when loadedLink / storybook path to visual changes
Integration
Does this contain changes to src/components or src/
Does this contain changes to src/features for brave-core?