Skip to content
This repository has been archived by the owner on Dec 5, 2024. It is now read-only.

Returning collection of requirement matchers is not properly processed when the same requirement class used #1990

Closed
odockal opened this issue Jan 28, 2019 · 0 comments
Assignees
Labels
Milestone

Comments

@odockal
Copy link
Collaborator

odockal commented Jan 28, 2019

Check method is evaluating collection of req. matchers in a wrong way. It throws and exception when there is more than one req. matcher with the same req. class, but should be thrown when there is the same req. class used with the same attribute.

@odockal odockal self-assigned this Jan 28, 2019
@odockal odockal added the bug label Jan 28, 2019
@odockal odockal added this to the 2.5.0 milestone Jan 28, 2019
odockal added a commit to odockal/reddeer that referenced this issue Jan 29, 2019
Signed-off-by: Ondrej Dockal <odockal@redhat.com>
odockal added a commit to odockal/reddeer that referenced this issue Feb 10, 2019
Signed-off-by: Ondrej Dockal <odockal@redhat.com>
odockal added a commit to odockal/reddeer that referenced this issue Feb 10, 2019
Signed-off-by: Ondrej Dockal <odockal@redhat.com>
jkopriva pushed a commit that referenced this issue Feb 12, 2019
Signed-off-by: Ondrej Dockal <odockal@redhat.com>
@odockal odockal closed this as completed Feb 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant