Skip to content

DATACMNS-1261 - Apply Java 8 Functional types and Lambdas to simplify… #274

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
wants to merge 1 commit into from

Conversation

jxblum
Copy link
Contributor

@jxblum jxblum commented Feb 17, 2018

… parsing logic in Repository configuration.

  • You have read the Spring Data contribution guidelines.
  • There is a ticket in the bug tracker for the project in our JIRA.
  • You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
  • You submit test cases (unit or integration tests) that back your 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).

@jxblum jxblum requested a review from odrotbohm February 17, 2018 00:29
@jxblum jxblum force-pushed the DATACMNS-1261 branch 3 times, most recently from 6b27587 to 4fd7e41 Compare February 22, 2018 23:09
… parsing logic in Repository configuration.

Additionally, fix up Exception error messages and edit Javadoc.
Copy link
Member

@mp911de mp911de left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR contains a lot of different things. Some things (like polishing) of ConfigurationUtils or some cases of Assert instead of throwing exceptions might make sense as a polishing PR.

throw new IllegalArgumentException(
String.format("Could not obtain required bean class name from BeanDefinition!", beanDefinition));
}
Assert.notNull(result, String.format("Could not obtain required bean class name from BeanDefinition [%s]!",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change has performance impact as String.format(…) is invoked regardless of whether it's required to. We should either stick with the previous variant or use a message supplier. There are also occurrences of similar changes.

* @see java.lang.Iterable
* @since 2.1.0
*/
public abstract class IterableUtils {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure that Spring Data is the best place for such a utility. I'd suggest to move it to Spring Framework.

@mp911de
Copy link
Member

mp911de commented Jan 11, 2021

Closing this pull request since there was no update since quite a while. We can reopen it if we want to revive it.

@mp911de mp911de closed this Jan 11, 2021
@mp911de mp911de added the status: declined A suggestion or change that we don't feel we should currently apply label Jan 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: declined A suggestion or change that we don't feel we should currently apply
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants