-
Notifications
You must be signed in to change notification settings - Fork 4
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.
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
do not allow selection to contain duplicates #489
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #489 +/- ##
==========================================
- Coverage 50.19% 49.70% -0.50%
==========================================
Files 26 26
Lines 2002 2010 +8
==========================================
- Hits 1005 999 -6
- Misses 997 1011 +14 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why don't you just filter duplicates in the selection rather than raising a ValueError?
My motivation was, to let the user know that duplicates will not be possible. When filtering them silently e.g. via |
Perhaps throw a warning instead? My worry is that something might happen in the webclient to accidentally cause a double selection. We don't want value errors thrown around in that case. |
The webclient uses a set for selection, so it should not be possible to cause any issue there: Line 71 in d61512a
|
In which case I think this is fine to merge. |
No description provided.