리팩토링 기준 #29
Replies: 11 comments 13 replies
-
|
Styled 컴포넌트 어디에 위치 시킬 것인지 |
Beta Was this translation helpful? Give feedback.
-
|
덜 중요하니까 아래로 갈까요? |
Beta Was this translation helpful? Give feedback.
-
|
넵 하단 위치로! |
Beta Was this translation helpful? Give feedback.
-
|
숫자 및 색상 상수화 |
Beta Was this translation helpful? Give feedback.
-
|
import 이후 개행 |
Beta Was this translation helpful? Give feedback.
-
|
쓰지 않는 import 문 삭제 |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
function 되어있는 것 const 형태로 바꾸기? |
Beta Was this translation helpful? Give feedback.
-
|
일관성 있게 const 선언형 방식으로 했으면 하네요! |
Beta Was this translation helpful? Give feedback.
-
|
페이지에 대한 라우트 path 정하기 |
Beta Was this translation helpful? Give feedback.
-
|
이건 우선 페이지 컴포넌트 이름으로 하는게 좋을 것 같아요! |
Beta Was this translation helpful? Give feedback.
-
|
console.log pr시 삭제 |
Beta Was this translation helpful? Give feedback.
-
|
앗 이건... 필수!!! |
Beta Was this translation helpful? Give feedback.
-
|
불필요한 주석 삭제 |
Beta Was this translation helpful? Give feedback.
-
|
한 함수에 15줄 미만으로 작성하기 |
Beta Was this translation helpful? Give feedback.
-
|
이건 꼭 제한을 하면 좋을까요? |
Beta Was this translation helpful? Give feedback.
-
|
함수가 너무 많은 역할을 수행하면 다른 사람이 코드를 파악하기 어려울 것 같아요 |
Beta Was this translation helpful? Give feedback.
-
|
어렵다고 느껴진다면 제한보다는 옵션으로 진행하는게 좋을 것 같네요 |
Beta Was this translation helpful? Give feedback.
-
|
Component 디렉토리 정리 많아지니 복잡합니다 |
Beta Was this translation helpful? Give feedback.
-
|
요건 개인 리팩토링하고, 다같이 정리하면 좋을 것 같네요! |
Beta Was this translation helpful? Give feedback.
-
|
역할이 최소화 + 많은 페이지에서 사용하고 있는 경우 |
Beta Was this translation helpful? Give feedback.
-
|
indent(인덴트, 들여쓰기) depth를 3이 넘지 않도록 구현하기 |
Beta Was this translation helpful? Give feedback.
-
|
if 같은 중첩문을 말씀하시는 것이군요 |
Beta Was this translation helpful? Give feedback.
-
|
넵 중첩문 반복문 등이 뎁스가 너무 깊어지면 흐름을 파악하기 어려워서요 |
Beta Was this translation helpful? Give feedback.
-
각자 생각하는 리팩토링의 기준을 적어주세요!
Beta Was this translation helpful? Give feedback.
All reactions