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.
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
[Bug] 버튼 연타 시 중복 호출 이슈 수정 #243
[Bug] 버튼 연타 시 중복 호출 이슈 수정 #243
Changes from 2 commits
4bfb6d1
0e41bf9
7d98e2b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
근본적으로 방지한다면, Navigate의 경우 PR에 작성해둔 것 처럼
navigate 시 이동할 destination과 currentDestination이 같지 않은 경우에만 이동
하도록 구현한다면 전체 상황에 대해서 방지할 수 있습니다.
뒤로가기의 경우에도 호출되는 모든 popBackStack 부분들에 때 의도하는 destination을 넘겨 해당 destination이 아닌 경우에만 뒤로가도록하는 방식을 채택한다면 마찬가지로 근본적으로 수정가능할 것 으로 보입니다.
다만 전반적으로 하나하나 연타를 해보았을 때 위의 시나리오 외에 중복 호출 되는 곳은 없어 적용하지 않았습니다. 만약 근본적인 차단을 고려하신다면 navigate, popBackStack하는 모든 부분들을 destination을 넘겨 받아 비교 후 처리하도록 구현하도록 하겠습니다. 😃
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.
넵, 아직은 확실하지 않은 기능이고 버그에 대한 이슈이므로 이정도로 괜찮을 것 같습니다.
확인 감사합니다