-
Notifications
You must be signed in to change notification settings - Fork 17
Change offset and count checks to undefined #141
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
Open
tomcss
wants to merge
1
commit into
RetroAchievements:main
Choose a base branch
from
tomcss:patch-1
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
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 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
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.
JavaScript callers can pass
null; this now serializeso=nullorc=nullinstead of omitting the parameter. The API can reject the request.Context Used: Be extremely concise in whatever you write on GitH... (source)
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.
Are you sure? The args are optionally typed as
foo?: number- not nullish.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.
You're right. With
foo?: number, TypeScript types it asnumber | undefined—nullis not assignable and can't be passed by a well-typed caller. The!== undefinedcheck in the PR is the correct and precise guard here. My suggestion was overly defensive. Good catch.Shall I remember this as a rule: "don't suggest
!= nullguards for parameters typed asfoo?: T—!== undefinedis the correct check sincenullisn't assignable to optional parameters"?Tip: You can customize Greptile's behavior for this repo with
.greptile/rules.mdand.greptile/config.json.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.
Yes, remember that as a rule.
Also - how many other files need to have
!== undefinedapplied to them for count / offset params for consistency?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.
Rule saved. View rule
Here's the full picture across the codebase:
5 files still using truthy checks (need fixing):
src/comment/getComments.tsif (offset)/if (count)src/leaderboard/getLeaderboardEntries.tsif (payload?.offset)/if (payload?.count)src/leaderboard/getUserGameLeaderboards.tsif (payload?.offset)/if (payload?.count)src/user/getUserWantToPlayList.tsif (payload?.offset)/if (payload?.count)src/feed/getRecentGameAwards.tsif (payload?.offset)/if (payload?.count)2 files already correct (no action needed):
src/user/getUsersIFollow.ts— uses!== null && !== undefined(redundant but safe; could be simplified to just!== undefined)src/user/getUsersFollowingMe.ts— same as aboveSo you have 5 files to update for consistency with this PR's fix.
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.
cc @tomcss can we propagate this for consistency everywhere else mentioned above