Skip to content
This repository has been archived by the owner on Nov 20, 2022. It is now read-only.

org.assertj.guava.data.MapEntry vs. org.assertj.core.data.MapEntry #44

Closed
scordio opened this issue Sep 30, 2019 · 0 comments
Closed

org.assertj.guava.data.MapEntry vs. org.assertj.core.data.MapEntry #44

scordio opened this issue Sep 30, 2019 · 0 comments

Comments

@scordio
Copy link
Member

scordio commented Sep 30, 2019

org.assertj.guava.data.MapEntry seems to be the same as org.assertj.core.data.MapEntry and the former is used only by RangeMapAssert#contains().

Having both in the same test scope can inhibit static imports.

I would suggest to deprecate org.assertj.guava.data.MapEntry together with the corresponding RangeMapAssert#contains(org.assertj.guava.data.MapEntry...) and to create a new RangeMapAssert#contains(org.assertj.core.data.MapEntry...).

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

No branches or pull requests

1 participant