-
Notifications
You must be signed in to change notification settings - Fork 8
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
Migrate screen via the site import link #543
Conversation
Migration screens
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.
- We need to group imports in all files based on our discussion. Example
- We also have a migrate button in the default flow that uses the migration URL. Should we make both of these behaviors consistent, or should we just remove the button from the default flow and keep it only on the fork step?
@@ -0,0 +1,85 @@ | |||
import { useEffect } from '@wordpress/element'; |
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.
Shall we reuse the existing error state? This one seems to be almost similar to the other one, and it does not handle mobile view, if I am not mistaken.
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.
It handles mobile view, I will check how can re-use the existing error state for migration as well.
src/OnboardingSPA/components/NewfoldInterfaceSkeleton/SiteBuild/index.js
Outdated
Show resolved
Hide resolved
|
||
const loadData = async () => { | ||
const migrateUrl = await getSiteMigrateUrl(); | ||
if ( migrateUrl?.body ) { |
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.
We need to check for response.error
instead of body
.
Co-authored-by: Arun Shenoy <[email protected]>
Co-authored-by: Arun Shenoy <[email protected]>
Ready for re-review @arunshenoy99 @officiallygod |
Proposed changes
Create Migration step for screens
https://www.figma.com/file/XlfIRs6b4vNPPK71HLLgrJ/Token-Flow?type=design&node-id=1447-57683&mode=design&t=doVZxjNrxswvueKi-0
Type of Change
Checklist
Further comments