-
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
개설자 본인은 공동 모임장 검색이 되지 않도록 구현 #949
Merged
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
any 가 있네요! any는 코드를 작성하는 때에는 문제가 없을지 몰라도.. 코드 수정 시에는 큰 문제가 될 수 있어요. 예를 들어, 만약 mentionUserList 에서 userId가 아닌 다른 값을 사용한다고 바뀌었다고 했을 때 타입에러가 발생하지 않으므로, 여기에서 userId 가 쓰인다는 사실을 모르게 되고, 이는 렌더링 시점에서 발생하는 에러이기 때문에, 사이트 전체가 터지게 되어요. (에러 바운더리를 쓰고 있다면, 가장 가까운 에러 바운더리에서 잡히게 되겠지만, 크루는 에러 바운더리조차 쓰고 있지 않기 때문에, 한 군데에서 문제가 터지면 사이트 전체가 터지게 됩니다..)
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.
any 정말 쓰고 싶진 않았는데 ㅠㅠ 지금 사용하고 있는 api에서 딱히 타입을 정의 안해줘서 any를 사용하긴 했어요!
api에서 타입을 정의해두지 않았던데, 이런 경우에는어떻게 해결하는게 좋을거라고 생각하시나요?
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.
mentionUser 에 대한 인터페이스를 api 응답값 참고해서 직접 만들어주면 어떨까요~!
참고로 저기에서 타입 지정하지 않은 이유는, 스웨거로 만든 타입에는 id, display 가 없는데 멘션 유저 타입에는 id, display 가 추가로 있어서 그런 거였어요. (이 두 개는 멘션 라이브러리에서 필요한 필드들)
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.
감사합니다 반영해두겠습니다 ~!