Details
-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: FEST-Assert 2.0
-
Fix Version/s: FEST-Assert 2.0
-
Component/s: Assert
-
Labels:
-
Number of attachments :
Description
Iterable is a more general interface and i think it makes sense to use it here (and maybe other places). For example it can be usefull when working with Spring DAOs - take a look at [1].
Activity
Joel Costigliola
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | FEST-Assert 2.0 [ 15576 ] |
Joel Costigliola
made changes -
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
I agree with that, we have "upgraded" collection assertions to Iterable assertions (thanks to Maciej Jaśkowski), we should also migrated isIn and isNotIn.
You can try to fix this issue, it should not be too complicated (I'll do it otherwise but I don't have much time these days).
We are on github here : https://github.com/alexruiz/fest-assert-2.x
And the contribution guide is here : https://github.com/alexruiz/fest-assert-2.x/wiki/Contributor-guidelines.
Cheers,
Joel