-
Notifications
You must be signed in to change notification settings - Fork 903
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
Use Brave Importer classes for auto-import #844
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah, my bad for previous #729 review because I forgot we have to use BraveExternalProcessImporterHost
LGTM, shouldn't this merge into master and cherry-pick into 0.56.x?
The current target branch is 0.56.x
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually why not just overriding ExternalProcessImporterHost
to BraveExternalProcessImporterHost
and ProfileWriter
to BraveProfileWriter
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
++
Use Brave Importer classes for auto-import
Use Brave Importer classes for auto-import
Use Brave Importer classes for auto-import
This reverts commit fd9849f. Reverting because we are doing a RC build for 0.56.x and did not intend this to be in the RC milestone.
Added back at the request of Garrett and Brian Bondy by reverting my revert with 68bc897 |
Resolves brave/brave-browser#2013.
Resolves brave/brave-browser#2014.
Submitter Checklist:
npm test brave_unit_tests && npm test brave_browser_tests
) ongit rebase master
(if needed).git rebase -i
to squash commits (if needed).Test Plan:
Follow test plans for brave/brave-browser#2013, brave/brave-browser#2014. Cookies and stats should be imported, where previously they were not.
Reviewer Checklist: