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

Pricing multiple adjustments #14

Merged
merged 2 commits into from
Jan 31, 2020

Conversation

dbrudner
Copy link
Contributor

No description provided.

@github-actions
Copy link
Contributor

Pull Request Test Coverage Report for Build 299c089fd607af5c8b1196f19ac0834cd8101c38-PR-14

  • 0 of 5 (0.0%) changed or added relevant lines in 1 file are covered.
  • 1 unchanged line in 1 file lost coverage.
  • Overall coverage decreased (-2.3%) to 48.026%

Changes Missing Coverage Covered Lines Changed/Added Lines %
lib/use-checkout-pricing.js 0 5 0.0%
Files with Coverage Reduction New Missed Lines %
lib/use-checkout-pricing.js 1 0%
Totals Coverage Status
Change from base Build 24869dbc1185ce9841cdb1b6b80434e6a0dbab13: -2.3%
Covered Lines: 55
Relevant Lines: 112

💛 - Coveralls

{recurlyError ? <span style={{ color: 'red' }}>{recurlyError.message}</span> : ''}
{price && price.now && !recurlyError ? <span>Subtotal: ${price.now.subtotal}</span> : ''}
</div>
<button>Calculate subtotal</button>
Copy link
Member

Choose a reason for hiding this comment

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

Is there a way to trigger recalculation onChange of any input without having to pepper onChange bindings throughout? I think that would be a more useful UX to demonstrate.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We can create a reusable input component for something like this. My intention was to abstract as little as possible, but the demo is definitely getting long and verbose.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I also think the demo generally needs some love. I'm thinking a separate PR everything else is merged in to clean up some demo-specific stuff is needed.

@chrissrogers chrissrogers merged commit e303dea into release/pricing Jan 31, 2020
@chrissrogers chrissrogers deleted the pricing-multiple-adjustments branch January 31, 2020 08:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants