-
Notifications
You must be signed in to change notification settings - Fork 2
style: Report와 Share 합치기 #254
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
base: develop
Are you sure you want to change the base?
Conversation
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/growto/team-grow-to-client/F89mutrxPV7pyk4Z68gMBwgyBpHf |
shji023
left a comment
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.
짱짱
small-j
left a comment
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.
고생했어요~
| `; | ||
|
|
||
| export const Wrapper = styled.article` | ||
| export const Wrapper = styled.div``; |
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.
wrapper안에 style코드가 들어가지 않고 그냥 태그를 명시하는 용도로만 사용되었는데 이 부분은 styled component가 아니라 그냥 div로 명시하는건 어떨까요?!
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.
흠 그러게 나도 이런 경우엔 div태그를 그냥 사용하긴 하는데 코드스타일마다 다른 것 같기도하고, , 합의가필요하려나?!
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.
아 그렇긴하네요 스타일로 더 명확한 의미로 표시한것 같기도 하고!
MainReport와 MainShare을 합쳐보겠습니다