-
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
마인더 정산신청 페이지 무한스크롤 오류 해결 및 DTO 업데이트 #415
Merged
Merged
Changes from 6 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
4abbe8e
Fix: solve infinite scroll issue
rmdnps10 234d66a
Fix: Reflect dto update contents
rmdnps10 9b3c246
Refactor: Remove unused SellerCalculateManagement component
rmdnps10 b1f204e
Refactor: Update SellerCalculateCard component to include consultDate…
rmdnps10 7364899
Fix: Reload page after completing apply in SellerCalculateManagement/…
rmdnps10 6425ca9
Fix: Update type annotation for 'res' as any
rmdnps10 3df9486
Refactor: Update CompleteApplyPopup and SellerCalculateCard components
rmdnps10 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
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.
혹시 여기서
reload
가 필요한 이유가 있을까요?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.
정산신청버튼을 누르고 팝업을 닫았을 경우에 데이터 최신화가 안되는 이슈가 있어서 reload()를 넣었습니다.. ㅎㅎ
정산예정 항목을 정산신청했을 경우에는 정산 중 항목으로 정산 예정항목이 넘어가게 되는데,
"정산 신청이 완료 되었습니다" 팝업을 닫았을 떄 페이지 새로고침을 강제하여 데이터가 최신화되게 하였습니다.
Reload하지말고 애초에 정산신청 클릭했을 때
manageList
서 필터링하는게 나을거같긴 한데 바꿀까요?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.
일단 filter한 list로 set해주는 로직 확인하였습니다 🫡
만약
react-query
를 사용한다면,invalidateQueries
를 사용하면 쉽게 구현할 수 있을 것 같네요!예를 들어 기존의 코드가 이렇게 구현되있다면, 먼저
useQuery
로 GET 요청을 하여 가져오는 로직으로 수정하고, 정산 신청 시 해당queryKey
를invalidateQueries
로 처리하면, 알아서useQuery
에서 해당 요청이 invalidate해진 걸 인지하고 다시 get 요청을 하게 됩니다.이런 식으로
react-query
로 구현하면 안정성 있게 구현할 수 있을 것 같네요!코스트가 많이 들 것 같다면 일단 머지하면 될 것 같습니다 고생하셨습니닷🫡
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.
코드 가독성과 안정성 측면에서 여러모로
tanstack-query
도입이 필요할 거 같습니다... 일단은 머지하고 마인더 쪽 코드에서 tanstack-query 리팩토링은 이슈 등록해서 한번에 진행해보겠습니다