Skip to content
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

시설, 찾아오는길 v2 read api + 진로 현황 CU api #323

Merged
merged 4 commits into from
Oct 19, 2024

Conversation

leeeryboy
Copy link
Contributor

시설, 찾아오는길 + 졸업생 진로 현황

한줄 요약

시설, 찾아오는길 v2 GET api, 졸업생 진로 현황 연도 추가, 연도별 수정 api

@leeeryboy leeeryboy requested a review from huGgW October 1, 2024 08:11
@leeeryboy leeeryboy self-assigned this Oct 1, 2024
Copy link

github-actions bot commented Oct 1, 2024

Test Results

11 files  11 suites   1s ⏱️
54 tests 54 ✔️ 0 💤 0
58 runs  58 ✔️ 0 💤 0

Results for commit 8114257.

♻️ This comment has been updated with latest results.

Copy link
Collaborator

@huGgW huGgW left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

코멘트 남긴것만 한번 확인해조!

Comment on lines +15 to +18
enum class Career(val krName: String) {
SAMSUNG("삼성"), LG("LG"), LARGE("기타 대기업"),
SMALL("중소기업"), GRADUATE("진학"), OTHER("기타")
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

이 부분 enum으로 한 이유가 있는거 아니면 그냥 string으로 하는게 나을듯..?
사실 이 부분이 변경될 가능성이 거의 없기야 해서 상관없을거 같긴 하지만

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

이상한 값 들어오는 거 방지 + 영어로 받아서 DB에는 기존과 같이 한글로 넣으려고 이렇게 했는데 string으로 하는게 나을거 같은 이유는 어떤 부분이야?

@leeeryboy leeeryboy merged commit 6e0dd59 into develop Oct 19, 2024
3 checks passed
@leeeryboy leeeryboy deleted the feat/read-about-v2 branch October 19, 2024 11:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants