fix: resolve null members in nested teams query - #11
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
teams { members { ... } }처럼 팀 안에서 멤버를 중첩 조회하면 멤버가 전부 null로 반환되는 버그를 고칩니다. 원인은Query.teams커넥터의 selection에 선언된members { login id }블록인데, GitHub의 팀 목록 API(/orgs/DaleStudy/teams) 응답에는members필드가 없어서 플래너가 이 필드들을 존재하지 않는 데이터에서 매핑하려다 non-null 위반으로 무너뜨립니다.