chore: standardize buttons using a button component

[MarioRodrigues10]

chore: use a Button component

[netlify]

✅ Deploy Preview for seium-stg ready!

Name	Link
🔨 Latest commit	aa1c16c
🔍 Latest deploy log	https://app.netlify.com/sites/seium-stg/deploys/65627f3a9bd8820008294562
😎 Deploy Preview	https://deploy-preview-571--seium-stg.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[diogogmatos]

Standardize buttons using a button component

[tiago-bacelar]

I feel like the title field could be a child component. I know 99% of the time it's text, but for the other 1% it would be really useful. Not to mention, it would be less verbose, more intuitive and better follow the composition model of react.

[Darguima]

I would suggest take the ...rest of the Button Props and pass it to the button element, to allow to use the generic HTML button props at the component level, without need future changes or extra complexity.

I think that if you don't want do this, at least you should correct the Props types with the Typescript Pick or Omit operators, because at this moment is correct, at the typescript level, pass any of the HTML buttons props to this component, even if they aren't used.

Also, if you want accept the changes I think that would be better the customStyle be the className (already included at ...rest) so as not to create confusion, since they would overwrite the other

[Darguima]

Perfect

Outdated