Split BtnLabeled into separate components

[andrewtavis]

Terms

• I have searched open and closed feature requests
• I agree to follow activist's Code of Conduct

Description

The BtnLabeled component is the most used component in activist – which is getting to be a problem. The assumption that one component should be holding the logic for almost all buttons on the platform is making it very difficult to add in new functionality. Specifically the need for a dropdown button in #473 raises the question of whether this should be included in the current component, with the breaks that this was causing indicating that these changes are now necessary.

The new implementation will:

• Save common props into TypeScript files
• Split buttons based on functionality
  • Actions like share, support, etc
  • Routes that are either internal or external
• Styles should also be extracted into commonly shared places in the code base

Contribution

I'm working on this now!

[andrewtavis]

The component was split in 6e637a9 - so all done 😊