-
Notifications
You must be signed in to change notification settings - Fork 238
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) Refactor modals to match naming conventions #1198
Conversation
Size Change: -17 kB (-0.49%) Total Size: 3.48 MB ℹ️ View Unchanged
|
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.
Code looks good, but I think we should standardize tests having a similar convention to the components they are tests for.
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.
Shouldn't this be named end-appointment.modal.test.tsx
?
We don't do component.test.tsx for test files, right? It's typically just the filename (sans the extension) ending with .test.tsx. Same for scss files (sorry about the lack of formatting - typed on my phone). |
@denniskigen Yeah, that's normally how we'd do it. I'm a little concerned about what happens when you have a component and, e.g., a modal that embeds that component. I.e., I'd rather let |
Yeah, I'd imagine that's unlikely. I'll merge this and review the situation post-merge once all the commits are in. |
Requirements
Summary
This PR refactors modal files to match the
*.modal.tsx
naming convention introduced in denniskigen/o3-docs#42 and other places.Screenshots
Related Issue
Other