-
Notifications
You must be signed in to change notification settings - Fork 6
Conversation
@@ -19,7 +19,7 @@ type Props = { | |||
isVisible: boolean; | |||
}; | |||
|
|||
export default function ThemePatterns( { isVisible }: Props ) { | |||
export default function Patterns( { isVisible }: Props ) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's also a Patterns
type, so this isn't great.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No conflict yet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh good point. I suppose we could just alias the Patterns
type when importing if there was a conflict. Or the component could be PatternsOverview
, though that's admittedly not what we're calling it 😆
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haha, yeah. It's a tough one, I blanked on different names.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice cleanup! These small changes are really useful in the long-term since things can be labelled in a newer, more accurate way.
@mike-day, |
ThemePatterns/
toPatterns/
ThemePatterns/
doesn't apply to Pattern Manager, though it was for FSE StudioHow to test
Not needed