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
Safer pagination and refresh for site cache #1239
Safer pagination and refresh for site cache #1239
Changes from 9 commits
59f3723
3ba96e3
14a141f
c0f9b6d
1a43437
475d999
f0a22d5
961ad24
3f2c4da
c5aef04
0337838
e3ad470
de741f1
027bc22
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 5 in src/config/config.ts
GitHub Actions / lint
Check warning on line 5 in src/config/config.ts
GitHub Actions / lint
Check warning on line 13 in src/config/config.ts
GitHub Actions / lint
Check warning on line 13 in src/config/config.ts
GitHub Actions / lint
Check warning on line 20 in src/config/config.ts
GitHub Actions / lint
Check warning on line 20 in src/config/config.ts
GitHub Actions / lint
Check warning on line 34 in src/config/config.ts
GitHub Actions / lint
Check warning on line 34 in src/config/config.ts
GitHub Actions / lint
Check warning on line 5 in src/constants/constants.ts
GitHub Actions / lint
Check warning on line 5 in src/constants/constants.ts
GitHub Actions / lint
Check warning on line 11 in src/constants/constants.ts
GitHub Actions / lint
Check warning on line 11 in src/constants/constants.ts
GitHub Actions / lint
Check warning on line 17 in src/constants/constants.ts
GitHub Actions / lint
Check warning on line 17 in src/constants/constants.ts
GitHub Actions / lint
Check warning on line 22 in src/constants/constants.ts
GitHub Actions / lint
Check warning on line 22 in src/constants/constants.ts
GitHub Actions / lint
Check warning on line 33 in src/constants/constants.ts
GitHub Actions / lint
Check warning on line 33 in src/constants/constants.ts
GitHub Actions / lint
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.
Note: this regex is not actually validating anything on the urls, or that
relid
should be one of"first" | "last" | "prev" | "next"
, even thought we do assert it in the types below withas IterableIterator<LinkMatch>
Because we are the one calling github, we trust their APIs, but we could add paranoia checks, and warning logging here 🤔
Or the regexp could be made more "validating" in that sense, like so for example, which would at least guarantee that
relid
is correct according to the type: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.
I'd rather leave the regexp loose tbh, in case github introduces more link relations in the future, they'd already be captured properly as part of the parsing routine.