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

Enhancement/9336 siwg setup page #9511

Merged
merged 22 commits into from
Oct 21, 2024

Conversation

zutigrm
Copy link
Collaborator

@zutigrm zutigrm commented Oct 15, 2024

Summary

Addresses issue:

Relevant technical choices

PR Author Checklist

  • My code is tested and passes existing unit tests.
  • My code has an appropriate set of unit tests which all pass.
  • My code is backward-compatible with WordPress 5.2 and PHP 7.4.
  • My code follows the WordPress coding standards.
  • My code has proper inline documentation.
  • I have added a QA Brief on the issue linked above.
  • I have signed the Contributor License Agreement (see https://cla.developers.google.com/).

Do not alter or remove anything below. The following sections will be managed by moderators only.

Code Reviewer Checklist

  • Run the code.
  • Ensure the acceptance criteria are satisfied.
  • Reassess the implementation with the IB.
  • Ensure no unrelated changes are included.
  • Ensure CI checks pass.
  • Check Storybook where applicable.
  • Ensure there is a QA Brief.
  • Ensure there are no unexpected significant changes to file sizes.

Merge Reviewer Checklist

  • Ensure the PR has the correct target branch.
  • Double-check that the PR is okay to be merged.
  • Ensure the corresponding issue has a ZenHub release assigned.
  • Add a changelog message to the issue.

Copy link

github-actions bot commented Oct 15, 2024

Build files for 64c878d have been deleted.

This comment was marked as resolved.

Copy link
Collaborator

@benbowler benbowler left a comment

Choose a reason for hiding this comment

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

Hey @zutigrm this was a good read and test, a couple of points:

  1. I noticed two issues with the SVG in different responsive sizes:

    1. At the smaller breakpoints there is a small ~1px white gap between the graphic and the footer:
    Screenshot 2024-10-16 at 09 54 43
    1. On larger screens the SVG is cropped or cut at the bottom cutting off the drop shadow of the graphic harshly:
    Screenshot 2024-10-16 at 09 55 07

One other note, this SetupFrom does not implement any error handling, should we implement something like the assets/js/components/StoreErrorNotices.js component in this setup form?

>
<LazyGraphicSVG />
</MediaErrorHandler>
</Suspense>
Copy link
Collaborator

Choose a reason for hiding this comment

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

Nice one for considering lazy loading here, that's something Evan has mentioned a few times recently and it something that should be considered in each ticket that adds new media.

@zutigrm
Copy link
Collaborator Author

zutigrm commented Oct 16, 2024

@benbowler Thanks, good catch!

On larger screens the SVG is cropped or cut at the bottom cutting off the drop shadow of the graphic harshly

Updated, thanks.

One other note, this SetupFrom does not implement any error handling, should we implement something like the assets/js/components/StoreErrorNotices.js component in this setup form?

StoreErrorNotices is already implemented in the form component:

<StoreErrorNotices
moduleSlug={ MODULES_SIGN_IN_WITH_GOOGLE }
storeName={ MODULES_SIGN_IN_WITH_GOOGLE }
/>

At the smaller breakpoints there is a small ~1px white gap between the graphic and the footer:

There isn't a space there, might be visual trick due to the grey border, since since there is no spacing between border and graphic:

image

Copy link
Collaborator

@benbowler benbowler left a comment

Choose a reason for hiding this comment

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

Thanks @zutigrm, there was a 1px gap here, I pushed a quick fix. All other points look good, moving through to MR.

Copy link
Collaborator

@eugene-manuilov eugene-manuilov left a comment

Choose a reason for hiding this comment

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

Thanks, @zutigrm. This is a good start. Added some feedback for you. Please, take a look.

Copy link
Collaborator

@eugene-manuilov eugene-manuilov left a comment

Choose a reason for hiding this comment

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

Thanks, @zutigrm. Almost looks good to me. Just added two last comments and it should be good to go.

import SetupForm from './SetupForm';
import Badge from '../../../../components/Badge';

export default function SetupMain( { finishSetup = () => {} } ) {
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think we can omit finishSetup for this component because we don't need it in the form component.

Suggested change
export default function SetupMain( { finishSetup = () => {} } ) {
export default function SetupMain() {

@eugene-manuilov eugene-manuilov merged commit 426909a into develop Oct 21, 2024
21 of 24 checks passed
@eugene-manuilov eugene-manuilov deleted the enhancement/9336-siwg-setup-page branch October 21, 2024 08:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants