Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: FEST-Assert 1.3
-
Fix Version/s: FEST-Assert 2.0
-
Component/s: Assert
-
Labels:None
-
Number of attachments :
Description
Method
org.fest.assertions.ObjectAssert.satisfies(Condition<Object>) and
org.fest.assertions.ObjectAssert.doesNotSatisfy(Condition<Object>)
declarations must be changed to
org.fest.assertions.ObjectAssert.satisfies(Condition<?>) and
org.fest.assertions.ObjectAssert.doesNotSatisfy(Condition<?>)
At present, there is only way to use this two methods is to implement Condition<Object> and make explicit type cast from Object to user type. It's inconvenient for common use.
Activity
Alex Ruiz
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Yvonne Wang [ wanghy ] | |
| Fix Version/s | FEST-Assert 1.3 [ 15940 ] |
Yvonne Wang
made changes -
| Status | Open [ 1 ] | In Progress [ 3 ] |
Alex Ruiz
made changes -
| Fix Version/s | FEST-Assert 2.0 [ 15576 ] | |
| Fix Version/s | FEST-Assert 1.3 [ 15940 ] |
Joel Costigliola
made changes -
| Assignee | Yvonne Wang [ wanghy ] | Joel Costigliola [ jocosti ] |
Joel Costigliola
made changes -
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
We tried to fix this issue, but it requires more thought than we thought. It is not just a simple replace of <Object> to <?>, due to the current object hierarchy in the project. We'll revisit this issue for FEST-Assert 2.0.