Skip to content

Documentation typo in BasicQuery class #4169

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
SPICYJO opened this issue Sep 18, 2022 · 0 comments
Closed

Documentation typo in BasicQuery class #4169

SPICYJO opened this issue Sep 18, 2022 · 0 comments
Assignees
Labels
type: documentation A documentation update

Comments

@SPICYJO
Copy link
Contributor

SPICYJO commented Sep 18, 2022

Hello,

I found a minor typo in documentation of BasicQuery.
I think sortObject should be changed to queryObject since this constructor does not have any parameter named sortObject.

* @throws IllegalArgumentException when {@code sortObject} or {@code fieldsObject} is {@literal null}.

Thank you for maintaining this awesome project!

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Sep 18, 2022
SPICYJO added a commit to SPICYJO/spring-data-mongodb that referenced this issue Sep 18, 2022
@mp911de mp911de added type: documentation A documentation update and removed status: waiting-for-triage An issue we've not yet triaged labels Sep 19, 2022
@mp911de mp911de self-assigned this Sep 19, 2022
@mp911de mp911de added this to the 3.3.8 (2021.1.8) milestone Sep 21, 2022
mp911de pushed a commit that referenced this issue Sep 21, 2022
Closes #4169
Original pull request: #4170.
mp911de pushed a commit that referenced this issue Sep 21, 2022
Closes #4169
Original pull request: #4170.
mp911de pushed a commit that referenced this issue Sep 21, 2022
Closes #4169
Original pull request: #4170.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: documentation A documentation update
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants