As amazing as styled-components are, not everyone uses it.
As such, having it as a requirement to use these components is adding un-needed package size bloat.

Since the core of these components is the BadgerBase higher-order-component, we should keep the size as minimal as possible.
If we want to build complex components using styled-components we may create a separate package for those in the future.

Update documentation on developer.bitcoin.com for 0.2.0

Topics to update

• Repeatable payments
• Absolute BCH amounts
• SLP if it makes it in this release
• QR Codes and URI
  • Watch all for payments
  • controlled step from app.

As these components API is gaining stability, it's time ensure the important code is tested correctly, especially for when additional people contribute to the projects.

Aiming for 75%+ testing coverage.

When building SLP token payments, it needs to be very clear which token one is sending.

• Show Symbol
• Show name
• Show correct decimal formatting.

Summary

• Images not rendering properly on Safari.
• Makes it unusable on iOS devices, and some versions of desktop Safari

Enable the react component to send SLP tokens using Badger.
Improve the UI to indicate the sending amount is in SLP tokens.

Along with this change should also enable sending an absolute amount of satoshis instead of converting from real world equivalents

Problem

Some use-cases, require the same button to be re-useable multiple times in a single visit.

Solution

• Add an optional prop to revert the state of the button to fresh after a payment is made
• Update documentation
• Update stories

• React and react-dom need a peerDepency of ^16.3.0

Summary

• BadgerBadge with QR code and URI support included

Custom Color Support

• Ability to either pass in N colors to use within the Button.
• To decide: Theme the button and BCH logo as well?
• Pass in colors OR a theme object compatible with styled-components

Colors to consider

• Background
• Foreground
• Brand - 500 and 700
  • Button fresh
  • Border
• Pending - 500 and 700
  • Button pending
• Success - 500 and 700
• Button success

Issue

Currently can only send amounts of BCH converted from their fiat currency equivalents.

Solution

Allow users to use props ticker/amount in addition of currency/price.
When ticker is used, create payments of an absolute amount.
When currency is used, create payments of BCH converted from price

These components need advanced error surfacing so users understand why the Badges are not working as they expect.
The component requires certain combinations of properties to work as intended, so when they are setup in an incompatible way, there should be a clear message with steps to correct them.

For complex applications which accept payments, the state of the payment should be validated and provided from the backend.

This issue is to add a property such as buttonState which will override the internal button step state.

Add support for OP_RETURN transactions

See here for reference
https://developer.bitcoin.com/badger/docs/send-bch

Documentation

Add documentation to developer.bitcoin.com on how to use, customize and create your own Badger integrations using our supplied components, as well as our Higher Order Components.

Usage

• Install
• Use a Badger Button - Embed example
• Use a BadgerBadge - Embed example
• Options
  • List props with descriptions - link to storybook page to try them out
• Limitations
  • Outline what they do, and what they can't do (Should use a server side to verify payments), these buttons assist, but are visual when it comes to security.
• Showcase
  • Examples of pages using parts of the library