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: [M3-6414, M3-6415] - MUIv5 Migration - Components > TagsInput, TagsPanel #8995

Merged
merged 7 commits into from
Apr 13, 2023

Conversation

hana-akamai
Copy link
Contributor

Description 📝

  • Migrate/modernize TagsPanel component from JSS to tss-react (Emotion)
  • Modernize TagsInput since it had no styles to migrate
  • Use named exports instead of default
  • Fix BetaChip story not rendering

How to test 🧪

  • Check places in the app where TagsInput and TagsPanel are used
  • Check that the TagsInput, TagsPanel, and BetaChip story renders in Storybook

Copy link
Contributor

@mjac0bs mjac0bs left a comment

Choose a reason for hiding this comment

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

No regressions that I could see. 🚢 And thanks for fixing the stories.

I have noticed that the BetaChip story is messed up somehow (actually, I think the component might be) because the chip in dark mode is not any different from different from light mode. And toggling the color in the Component API has no effect. But that's pretty far out of the intended scope this PR.

Screenshot 2023-04-12 at 2 48 15 PM

packages/manager/src/components/TagsInput/TagsInput.tsx Outdated Show resolved Hide resolved
@mjac0bs
Copy link
Contributor

mjac0bs commented Apr 13, 2023

@hana-linode Let's add a Tech Stories section and changelog entry before this is merged in!

@hana-akamai hana-akamai merged commit 394e8d4 into linode:develop Apr 13, 2023
@hana-akamai hana-akamai deleted the M3-6415-tags-panel branch April 13, 2023 20:04
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.

4 participants