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

Feat/fixSLStyling #1440

Merged
merged 7 commits into from
Mar 13, 2024
Merged

Feat/fixSLStyling #1440

merged 7 commits into from
Mar 13, 2024

Conversation

kishore03109
Copy link
Contributor

@kishore03109 kishore03109 commented Aug 23, 2023

Problem

Currently storybooks cannot toggle the steps, design found it harder to review + write a guide for SL
This also fixes trivial copy issues.

Solution

Change API so the increaseStepNumber and the decreaseStepNumber both come from the context directly, similar to the increasePageNumber + decreaseStepNumber.
For Verbosity, I have also added 4 screens for design to review + increase possibilities of catching regression when other devs develop SL in the future.

Breaking Changes

  • Yes - this PR contains breaking changes
    • Details ...
  • No - this PR is backwards compatible

Before & After Screenshots

AFTER:
Storybook check boxes should work

New Domain:
https://github.com/isomerpages/isomercms-frontend/assets/42832651/981f7417-4c6f-48d8-a34c-61d2609f38c9

Old Domain:
https://github.com/isomerpages/isomercms-frontend/assets/42832651/6cee2d80-3afe-4609-b2b3-c01844e59661

4 added storybooks:
A: new-domain-non-www-dns-records
Screenshot 2023-08-23 at 3 34 43 PM

B: new-domain-www-dns-records
Screenshot 2023-08-23 at 3 34 59 PM

C: old-domain-non-www-dns-records
Screenshot 2023-08-23 at 3 35 09 PM

D: old-domain-www-dns-records
Screenshot 2023-08-23 at 3 35 20 PM

Now copied got tooltip:
Screenshot 2023-08-23 at 3 32 35 PM

Tests

None, mostly to sped up reviewal + trivial copy changes

@kishore03109 kishore03109 temporarily deployed to staging August 23, 2023 07:17 — with GitHub Actions Inactive
@kishore03109 kishore03109 temporarily deployed to staging August 23, 2023 07:18 — with GitHub Actions Inactive
@kishore03109 kishore03109 marked this pull request as ready for review August 23, 2023 07:47
@kishore03109 kishore03109 requested review from seaerchin and a team and removed request for seaerchin August 23, 2023 07:48
@kishore03109 kishore03109 temporarily deployed to staging August 23, 2023 07:57 — with GitHub Actions Inactive
Copy link
Contributor

@seaerchin seaerchin left a comment

Choose a reason for hiding this comment

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

no functional blockers but we should avoid temptation to stuff everything into context

@@ -79,7 +83,7 @@ export const SiteLaunchProvider = ({
})

const { data: siteLaunchDto } = useGetSiteLaunchStatus(siteName)

console.log({ siteLaunchDto })
Copy link
Contributor

Choose a reason for hiding this comment

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

Sir.

Comment on lines +34 to +35
handleIncrementStepNumber: () => void
handleDecrementStepNumber: () => void
Copy link
Contributor

Choose a reason for hiding this comment

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

we need to take care to prevent props explosion here. this is not an issue for now because idt we will have active work going on for site launch, but we want to avoid the case where we just put everything here and ignore proper component structure, which will impact maintainability in the future.

tl;dr: is ok but we should avoid adding stuff here already.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

can, but for future ref may I trouble you to explain how I could make this more maintainable + allow storybook to be versatile enough to be able to click thr the checkboxes? I am abit unsure of how I could have made this PR better in the future

Copy link
Contributor

Choose a reason for hiding this comment

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

without pair programming/actually working on this portion of the codebase, it's bit difficult to actually find something that works well. 1 sign that you could use to signal for help could be that you find yourself needing the context for everything, which shouldn't be the case.

1 thing that you can try is to see which parts of the state your child components truly need and refactoring so that you pass that state to your children. i've done htis here because the two nested components were p disjoint in their props but only really needed the selectedOption

Comment on lines +87 to +89
whiteSpace="nowrap"
overflow="hidden"
textOverflow="ellipsis"
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: prefer noOfLines

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Screenshot 2023-08-23 at 5 29 27 PM somehow when I use `noOfLines`, the `...` (ellipsis) effect disappears, do you know why?

Copy link
Contributor

Choose a reason for hiding this comment

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

have to check the styling - the Text hasn't overflowed its bounding box yet i think

Copy link
Contributor

Choose a reason for hiding this comment

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

cos from the docs here, it should display ellipsis (and in prior experience, it has)

@kishore03109 kishore03109 temporarily deployed to staging August 23, 2023 09:50 — with GitHub Actions Inactive
@mergify mergify bot requested a review from a team October 7, 2023 04:31
@mergify
Copy link

mergify bot commented Oct 7, 2023

This pull request has been stale for more than 30 days! Could someone please take a look at it @isomerpages/iso-engineers

1 similar comment
Copy link

mergify bot commented Nov 6, 2023

This pull request has been stale for more than 30 days! Could someone please take a look at it @isomerpages/iso-engineers

@kishore03109 kishore03109 added 2019 and removed 2019 labels Dec 21, 2023
Copy link

mergify bot commented Jan 20, 2024

This pull request has been stale for more than 30 days! Could someone please take a look at it @isomerpages/iso-engineers

2 similar comments
Copy link

mergify bot commented Feb 19, 2024

This pull request has been stale for more than 30 days! Could someone please take a look at it @isomerpages/iso-engineers

Copy link

mergify bot commented Mar 7, 2024

This pull request has been stale for more than 30 days! Could someone please take a look at it @isomerpages/iso-engineers

@kishore03109 kishore03109 merged commit ec1ce26 into develop Mar 13, 2024
@mergify mergify bot deleted the feat/fixSLStyling branch March 13, 2024 07:15
@dcshzj dcshzj mentioned this pull request Mar 14, 2024
3 tasks
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.

2 participants