fix: Add optional to type chain #560
Merged
Conversation
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
There was a problem hiding this comment.
should probably also include a test -- here's the actual api body for the PR which may be helpful in crafting a fake graphql response for a test https://api.github.com/repos/getsentry/jsonnet-libs/pulls/5
src/utils/changelog.ts
Outdated
| @@ -472,7 +472,7 @@ async function getPRAndMilestoneFromCommit( | |||
| hash.slice(1), | |||
| pr | |||
| ? { | |||
| author: pr.author.login, | |||
| author: pr.author?.login ?? null, | |||
There was a problem hiding this comment.
I don't think ?? null is needed here with the ?. access (since that'll become undefined already) -- I think this also needs a fix to the types above because as it is right now the ?. looks unnecessary (I'm surprised the type checker isn't complaining about this?)
asottile-sentry
approved these changes
Oct 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR fixes #559