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.
이벤트 드라이븐 방식으로 작동하고있고 Consume 한 뒤에 StageCaller가 Stage를 호출 후에 다음 Stage를 nextStageCall을 해야하는데 어느쪽에서 nextStageCall을 하면 좋을지 모르겠습니다.
StageCall에서 nextStageCall 하기
이것도 나쁘지않는데 이렇게 하면 stageCall의 원래 기능은 단순하게 현재의 파라미터에 맞는 단계의 stage를 call하는건데 자동으로 nextStageCall을 까지 하게되면 기능이 무너질듯합니다.
Stage 수행단계에서 nextStageCall 호출하기
이것도 괜찮긴한데... 뭔가 어색하고 코드 중복이 많아질듯합니다