-
Notifications
You must be signed in to change notification settings - Fork 94
make defacto public fields actually public #1526
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
Closed
sunshowers
wants to merge
1
commit into
main
from
sunshowers/spr/make-defacto-public-fields-actually-public
Closed
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -237,7 +237,7 @@ where | |
| /// Consumers should use | ||
| /// [`RequestContext`][crate::handler::RequestContext::page_limit()] | ||
| /// to access this value. | ||
| pub(crate) limit: Option<NonZeroU32>, | ||
| pub limit: Option<NonZeroU32>, | ||
| } | ||
|
|
||
| pub(crate) const PAGINATION_PARAM_SENTINEL: &str = | ||
|
|
@@ -420,8 +420,8 @@ enum PaginationVersion { | |
| /// Parts of the pagination token that actually get serialized | ||
| #[derive(Debug, Deserialize, Serialize)] | ||
| struct SerializedToken<PageSelector> { | ||
| v: PaginationVersion, | ||
| page_start: PageSelector, | ||
| pub v: PaginationVersion, | ||
| pub page_start: PageSelector, | ||
|
Comment on lines
422
to
+424
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm not sure I follow--this type isn't public, right?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ah yeah this type isn't public, my bad |
||
| } | ||
|
|
||
| /// Construct a serialized page token from a consumer's page selector | ||
|
|
||
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.
what about this? I'm not sure I recall the rationale here; perhaps to preserve our ability to change things in the future?
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.
It's not possible to preserve the ability without a breaking change, since this is directly exposed in the HTTP endpoint.
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.
Mentioned elsewhere but so this is not lost: the reason this is not
pubis because it is almost certainly the wrong thing for consumers to read it so it would be a footgun to expose it to them. They should be usingpage_limit(). (This field is the limit the user (untrusted) may have provided.page_limit()looks at this, but validates it (if specified) and provides a default (if not).)