Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Should BeanPopulationException be a unchecked (runtime) exception? #63

Closed
PascalSchumacher opened this issue Feb 5, 2016 · 1 comment
Closed

Should BeanPopulationException be a unchecked (runtime) exception? #63

PascalSchumacher opened this issue Feb 5, 2016 · 1 comment
Assignees
@fmbenhassine
Labels
question
Milestone
2.0.0

Comments

@PascalSchumacher
Copy link
Collaborator

I personally like to be able to write unit tests without adding "throws Exception" to every signature.

But others may disagree.
@PascalSchumacher PascalSchumacher changed the title Should BeanPopulationException be a unchecked (RuntimeException)? Should BeanPopulationException be a unchecked (runtime) exception? Feb 5, 2016
@fmbenhassine fmbenhassine added this to the 2.0.0 milestone Feb 6, 2016
@fmbenhassine fmbenhassine self-assigned this Feb 6, 2016
fmbenhassine added a commit that referenced this issue Feb 6, 2016
@fmbenhassine
fix issue #63 : Make BeanPopulationException unchecked
213ef77
@fmbenhassine
Copy link
Member

This exception has been requested in issue #39 .
I just turned it into a RuntimeException, this is better indeed.
The user can still catch it and make the test fails if needed.

@fmbenhassine fmbenhassine mentioned this issue Feb 21, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fmbenhassine fmbenhassine

Labels
question
Projects
None yet
Milestone
2.0.0
Development

No branches or pull requests
2 participants
@fmbenhassine @PascalSchumacher