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

CHECKOUT-1967 Resolve Accessibility Issues #1061

Merged
merged 1 commit into from
Sep 7, 2017

Conversation

icatalina
Copy link
Contributor

What?

Adding some missing customisation options for Optimized Checkout so merchants can fully tailor the shopper experience and be fully accessible.

Tickets / Documentation

Screenshots (if appropriate)

On their way 😊

Copy link
Contributor

@davidchin davidchin left a comment

Choose a reason for hiding this comment

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

Looking good so far, nice work 👏

// Styles form fields.
// -----------------------------------------------------------------------------

.optimizedCheckout-form-input {
$optmizedCheckout-inputBoxShadow: inset 0 1px 1px stencilColor("optimizedCheckout-formField-shadowColor");
Copy link
Contributor

Choose a reason for hiding this comment

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

You have a spelling mistake here: optmizedCheckout -> optimizedCheckout :)

Copy link
Contributor

Choose a reason for hiding this comment

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

Also, I think we have a specific way of naming SASS variables (i.e.: https://github.com/bigcommerce/sass-style-guide#variables). Do you want to follow that?

@mcampa
Copy link
Contributor

mcampa commented Aug 8, 2017

The schema file is crazy big right now in Cornertone, and ThemeEditor was not really designed to support so many fields from the schema. This is going to slow down ThemeEditor.

I'm not opposing this change, just something to think about. If you have the chance, please take a look a TE to see how we can improve performance.

@davidchin
Copy link
Contributor

@mcampa very good point. I agree we can look into improving the performance of TE separately. :)

@icatalina icatalina force-pushed the CHECKOUT-1967 branch 3 times, most recently from ca0ce8b to 41baea4 Compare August 23, 2017 04:55
@icatalina
Copy link
Contributor Author

I tackled those issues... please have a look 🙂

Copy link
Contributor

@davidchin davidchin left a comment

Choose a reason for hiding this comment

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

LGTM, nice work!

@icatalina icatalina changed the title WIP: CHECKOUT-1967 Resolve Accessibility Issues CHECKOUT-1967 Resolve Accessibility Issues Aug 23, 2017
@junedkazi
Copy link
Contributor

can we get some screenshots & a QE sign off since it has lots of changes to the schema.

@davidchin
Copy link
Contributor

Hey @junedkazi, thanks for checking. We already reached out to Jully, hoping that one of the QEs / designers from Stencil team can help verify the changes in the upcoming sprint. There's a separate ticket tracking the QA work (STENCIL-3751). :)

@mjschock
Copy link
Contributor

@icatalina - could you rebase into one commit and add a changelog entry?

@icatalina
Copy link
Contributor Author

@mjschock For sure...

@icatalina
Copy link
Contributor Author

I let it like this because it is easier to review...

@icatalina icatalina force-pushed the CHECKOUT-1967 branch 2 times, most recently from ec0b222 to f715198 Compare September 3, 2017 23:09
@icatalina
Copy link
Contributor Author

Hi @mjschock!,

All squashed and change log added. I've kept a copy not squashed just in case it makes it easier to review: https://github.com/icatalina/cornerstone/tree/CHECKOUT-1967-unsquash

Could you please have a look and confirm you're happy with these changes?

Kind Regards,
Ignacio Catalina

@icatalina
Copy link
Contributor Author

icatalina commented Sep 6, 2017

Some screenshots:

Light Before After
Home light home org light home new
Product light product org light product new
Cart light cart org light cart new
Checkout light checkout org light checkout new
Warm Before After
Home warm home org warm home new
Product warm product org warm product new
Cart warm cart org warm cart new
Checkout warm checkout org warm checkout new
Dark Before After
Home dark home org dark home new
Product dark product org dark product new
Cart dark cart org dark cart new
Checkout dark checkout org dark checkout new

schema.json Outdated
@@ -1,2498 +1,2626 @@
[
Copy link
Contributor

Choose a reason for hiding this comment

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

@icatalina - is there a way to get the changes in here without causing the entire schema to differ?

@mjschock mjschock self-assigned this Sep 6, 2017
Copy link
Contributor

@mjschock mjschock left a comment

Choose a reason for hiding this comment

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

@icatalina - i have a question about the schema changes and there's a conflict with the CHANGELOG. besides that, these changes LGTM.

@icatalina
Copy link
Contributor Author

I tackled @mjschock concerns... I'll raise a different PR for changing the schema.json format to unix.

@davidchin
Copy link
Contributor

davidchin commented Sep 7, 2017

I think it makes sense to squash commits that cannot be checked out individually (i.e.: WIP commits). If each commit is an incremental change that is descriptive and comprehensible, I don't think it's strictly necessary to squash them into one.

  • Firstly, it's easier for reviewers to review the changes.
  • Secondly, it's easier for the team to look at the history and go back in time when things break.
  • Thirdly, it's easier to break the PR into multiple ones if it contains multiple unrelated changes which should be submitted separately.

Having said that, sometimes, it's actually easier to review the changes or check the history if the commits are squashed into one (or fewer ones). In that case, yes, we should squash the commits. So I think it really depends on the situation. We shouldn't squash the commits just because we need to follow a rule. Anyway, just my two cents 😄

@icatalina icatalina merged commit dd4cfe1 into bigcommerce:master Sep 7, 2017
@icatalina icatalina deleted the CHECKOUT-1967 branch September 7, 2017 23:25
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.

5 participants