Skip to content

#594 - Protect against Spring 5 non-null inputs #595

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
Closed

Conversation

gregturn
Copy link
Contributor

@gregturn gregturn commented Jun 7, 2017

Spring 5 has adopted a "no nulls" policy that causes certain methods to throw exceptions instead of returning a null. This updates Spring HATEOAS to handle it suitably.

Spring 5 has adopted a "no nulls" policy that causes certain methods to throw exceptions instead of returning a null. This updates Spring HATEOAS to handle it suitably.
@gregturn gregturn requested a review from odrotbohm June 7, 2017 14:46
@gregturn gregturn self-assigned this Jun 7, 2017
odrotbohm pushed a commit that referenced this pull request Jul 27, 2017
Spring 5 has adopted a "no nulls" policy that causes certain methods to throw exceptions instead of returning a null. This updates Spring HATEOAS to handle it suitably.

Original pull request: #595.
odrotbohm added a commit that referenced this pull request Jul 27, 2017
Rather use early return for null annotation instead of conditional lookup.

Original pull request: #595.
@odrotbohm
Copy link
Member

That's merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants