-
Notifications
You must be signed in to change notification settings - Fork 0
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
chat main component (after #4 merged) #6
base: dev
Are you sure you want to change the base?
Conversation
swc, storybook 설정 및 feedback list 컴포넌트 추가
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 mainInfoStyle = css` | ||
/* padding: 0 1.5rem; */ | ||
`; |
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 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.
앗 지우겠습니다 ㅎㅎ..
display: -webkit-box; | ||
-webkit-box-orient: vertical; | ||
-webkit-line-clamp: 3; |
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.
webkit 속성을 사용하신 이유가 궁금하네요 :)
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 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.
표준이 아니다보니 엣지나 파폭은 안먹힐것 같아서요 ㅠㅠ
라인수 제한을 꼭 해야 하는 걸까용??
<path | ||
d="M75 10 L 25 50 L 75 90" | ||
css={[{ stroke: color }, backPathDefaultStyle]} | ||
/> |
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.
오 path 태그로 구현하셨군요... 대박
color: string; | ||
} | ||
|
||
const Exit: FC<ButtonProps> = ({ width, height, color }) => { |
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.
피그마에 있는 svg, png 파일이 아닌 이렇게 직접 구현하신 이유가 궁금합니다!?
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.
한번 해보고 싶었습니다.. 간단한 path니깐요 ㅋㅋㅋㅋ
colorPrimary: string; | ||
colorPrimaryDark: string; | ||
colorPrimaryLight: string; | ||
colorSub: string; | ||
colorSubLight: string; | ||
colorBg: string; | ||
colorWhite: string; | ||
colorGray1: string; | ||
colorGray2: string; | ||
colorGray3: string; | ||
colorIndigo: string; | ||
colorBrown: string; | ||
colorSuccess: string; | ||
colorError: string; | ||
|
||
fontBasic: string; | ||
fontCoding: string; | ||
fontCodingBold: string; |
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.
기존에 있는 타입을 지우고 인덱스 시그니처를 사용하신 이유가 있을까요??
이전과 달리 Theme가 너무 큰 범위의 프로퍼티 타입을 가지게 되는것 아닐까요?
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.
이건 이전에 수정할 때 상황에 따라 theme이 달라지도록 하려다보니 일단 바꿨습니다..
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.
혹시 지난 PR dev merge 후 변경사항이 아직 남아있는 것 같은데, rebase 한 번만 해주실 수 있을까요?!!
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.
dev rebase는 확인해보니 되어있는데 이전 swc 관련 변경사항들이 보이는 것 같네요!! 무슨 문제일까용? 👀
확실히 storybook 보니까 PR 리뷰 하면서 스스로 테스트해본걸 storybook 통해서 쉽게쉽게 볼 수 있어서 정말 좋네요 !!! ㅎㅎㅎ
지난 회의 시간에 컴포넌트 분리 기준에 대해 말씀해주신게 왜 고민이 되었는지 이해가 되네요!!!
몇가지 코멘트 남겨보았습니닷 👍🏻
// @TODO: primary 정보를 가져와 어떤 theme을 전달할지 결정해야 합니다. | ||
const isPrimary = true; | ||
return ( | ||
<BrowserRouter> | ||
<RecoilRoot> | ||
<ThemeProvider theme={isPrimary ? primaryTheme : subTheme}> |
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.
ThemeProvider 좋네용 !!! 👍🏻👍🏻👍🏻
const ProjectIntro: FC<ProjectIntroProps> = ({ name, description }) => { | ||
// @TODO: 버튼 클릭시 채팅 컴포넌트로 넘어가도록 해야합니다. |
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.
어떤 버튼 클릭시인가요?
const TelbbyServiceClient: FC = () => { | ||
// @TODO 여기에서 Service Client를 구현해나갑니다. | ||
return <div css={chatMainDefaultStyle} />; | ||
}; |
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.
TelbbyServiceClient 컴포넌트를 Main 컴포넌트 밑에 위치시킨 이유는 무엇일까요?
color: string; | ||
} | ||
|
||
const Exit: FC<ButtonProps> = ({ width, height, color }) => { |
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.
BackBtn인데 Exit이라고 네이밍을 잘못 해둔 것 같네요!!
그리고 Main 밑에는 BottomButton 이라고 버튼을 풀네임으로 쓰고, common 밑에는 BackBtn, ExitBtn으로 줄여서 써서 이 부분 통일하면 좋을 것 같아요!
LightExitButton.decorators = [ | ||
(Story) => { | ||
return ( | ||
<div style={{ backgroundColor: theme.colorPrimary }}> | ||
<Story /> |
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.
오호 이렇게도 가능하군요!!!
개요
chat main component와 필요한 이외의 common 컴포넌트도 작성하였습니다.
이슈 번호
변경사항
특이사항