Skip to content
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

Merged
merged 45 commits into from
May 3, 2024
Merged

Migrate screen via the site import link #543

merged 45 commits into from
May 3, 2024

Conversation

ajayadav09
Copy link
Contributor

@ajayadav09 ajayadav09 commented Apr 16, 2024

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

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices apply)

Checklist

  • I have read the CONTRIBUTING doc
  • Linting and tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

Further comments

@ajayadav09 ajayadav09 added the WIP PR is a Work in Progress and not ready for review. label Apr 16, 2024
@ajayadav09 ajayadav09 added Code Review The PR is in Code Review and removed WIP PR is a Work in Progress and not ready for review. labels Apr 25, 2024
Copy link
Member

@arunshenoy99 arunshenoy99 left a comment

Choose a reason for hiding this comment

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

  1. We need to group imports in all files based on our discussion. Example
  2. 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?
    image

@@ -0,0 +1,85 @@
import { useEffect } from '@wordpress/element';
Copy link
Member

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.

Copy link
Contributor Author

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/data/flows/default.js Outdated Show resolved Hide resolved
src/OnboardingSPA/steps/SiteGen/Migration/contents.js Outdated Show resolved Hide resolved
src/OnboardingSPA/steps/SiteGen/Migration/index.js Outdated Show resolved Hide resolved
src/OnboardingSPA/styles/app.scss Show resolved Hide resolved
src/constants.js Show resolved Hide resolved

const loadData = async () => {
const migrateUrl = await getSiteMigrateUrl();
if ( migrateUrl?.body ) {
Copy link
Member

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.

src/OnboardingSPA/steps/SiteGen/Migration/index.js Outdated Show resolved Hide resolved
src/OnboardingSPA/steps/SiteGen/Migration/index.js Outdated Show resolved Hide resolved
@ajayadav09 ajayadav09 requested a review from arunshenoy99 April 29, 2024 17:39
@ajayadav09
Copy link
Contributor Author

ajayadav09 commented Apr 29, 2024

Ready for re-review @arunshenoy99 @officiallygod

@arunshenoy99 arunshenoy99 added QA This PR is in QA and removed Code Review The PR is in Code Review labels May 2, 2024
@arunshenoy99 arunshenoy99 merged commit 60f917c into trunk May 3, 2024
1 of 4 checks passed
@arunshenoy99 arunshenoy99 deleted the migrate-screen branch May 3, 2024 10:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
QA This PR is in QA
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants