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

Refactor: Replace old button with new button components #2212

Merged
merged 9 commits into from
Feb 19, 2025

Conversation

NSUWAL123
Copy link
Contributor

What type of PR is this? (check all applicable)

  • πŸ• Feature
  • πŸ› Bug Fix
  • πŸ“ Documentation
  • πŸ§‘β€πŸ’» Refactor
  • βœ… Test
  • πŸ€– Build or CI
  • ❓ Other (please specify)

Related Issue

Previously, a new button component was made which needed to be replaced with the old button component

Describe this PR

  • Replace of previously used old button components with new button components overall

Screenshots

image

@NSUWAL123 NSUWAL123 requested a review from spwoodcock February 19, 2025 08:40
@github-actions github-actions bot added enhancement New feature or request frontend Related to frontend code labels Feb 19, 2025
Copy link
Member

@spwoodcock spwoodcock left a comment

Choose a reason for hiding this comment

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

Love this idea overall πŸŽ‰

But was wondering if in the long run we can replace components like buttons designed for FMTM with generic button components from shoelace-style?

Similar to the components we have integrated into the mapper frontend.

React 19 has first party support for web-components, so it should work well

@spwoodcock spwoodcock merged commit ac12929 into development Feb 19, 2025
6 checks passed
@spwoodcock spwoodcock deleted the refactor/replace-old-buttons branch February 19, 2025 13:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request frontend Related to frontend code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants