EP-2261: BCO Premium Selection

[reldredge71]

Allows users to select a premium on branded checkout

[wrandall22]

There are still several references to radio station codes.

[wrandall22]

Feel free to merge it to staging locally after Travis passes here.

[reldredge71]

@wrandall22 I was working on Mike's request for an anchor on branded-checkout-step-1 to jump to the Premium section. I was having some difficulty with this, and it might not be the highest priority right now, but I did notice that the user's choice for the Premium selection was getting overwritten when navigating back to branded-checkout-step-1. I made an update here to make sure that the choice the user made will still appear when reversing steps.

Do you think I should still attempt to get the anchoring to work?

[wrandall22]

As far as anchoring...None of the other Change buttons go to a particular part of the page, outside of just the branded checkout component itself. That might be worth mentioning to Mike. It would be a new pattern not followed by the rest of the branded checkout.

[wrandall22]

I think part of the reason is that the branded checkout component has to load, and the anchoring probably happens before it loads completely, so anchoring into some HTML that doesn't yet exist will likely have issues.

[reldredge71]

Yes, when I saw that the sections of the checkout screen passed unique string values to changeStep, it made me think that anchoring was possible... then I realized that none of the sections had that functionality yet. I agree that timing the anchor navigation with the loading of the screen would be tricky. I can mention that to Mike.

[wrandall22]

I think that functionality is more used on standard checkout, where those steps are actually on different pages.

[reldredge71]

After I resolve the conflicts and rebase this on top of master, should I go ahead and merge this? John will need this to add the premium functionality to the plugin.

[wrandall22]

Is the plugin on stage pointing at the production branded checkout? That would be problematic...

[reldredge71]

@wrandall22 I guess I misunderstood what John told me earlier today. He is able to work with Premiums on staging, and the plugin on staging uses the staging Branded Checkout. He was wondering why the Premium attributes were not in the README on production, but I think he has what he needs to work on this.

Do you think I should merge this in still? Or do we want to wait and see if FamilyLife wants the placement of the Premium fields to be changed?

[wrandall22]

I think we should wait for their feedback on placement.

[wrandall22]

The last 2 commits could have their descriptions improved. What is happening in those commits is not what is described by the commit messages.

[wrandall22]

Thanks for making those updates! If you get these changes out on staging that will be helpful (if you haven't already).

[caleballdrin]

@wrandall22 it is on staging

[wrandall22]

Found a couple minor things while implementing AEM piece.