Skip to content

Remove unnecessary toString() call. #2431

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

Conversation

DiegoKrupitza
Copy link
Contributor

There were few explicit toString() calls that are not needed, since toString() will be called by default.

  • You have read the Spring Data contribution guidelines.
  • You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
  • You added yourself as author in the headers of the classes you touched. Amend the date range in the Apache license header if needed. For new types, add the license header (copy from another file and set the current year only).

There were few explicit `toString()` calls that are not needed, since `toString()` will be called by default.
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Feb 7, 2022
schauder pushed a commit that referenced this pull request Feb 7, 2022
There were few explicit `toString()` calls that are not needed, since `toString()` will be called by default.

Original pull request #2431
@schauder
Copy link
Contributor

schauder commented Feb 7, 2022

Thanks, that's merged.

@schauder schauder closed this Feb 7, 2022
@schauder schauder added type: task A general task and removed status: waiting-for-triage An issue we've not yet triaged labels Feb 7, 2022
schauder pushed a commit that referenced this pull request Feb 15, 2022
There were few explicit `toString()` calls that are not needed, since `toString()` will be called by default.

Original pull request #2431
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: task A general task
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants