-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
negative datanames selection #1426
Conversation
Code Coverage Summary
Diff against main
Results for commit: 0d776a4 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
Unit Tests Summary 1 files 27 suites 8m 59s ⏱️ Results for commit 0d776a4. ♻️ This comment has been updated with latest results. |
Unit Test Performance Difference
Results for commit 1fc760f ♻️ This comment has been updated with latest results. |
I'll try another solution which will add a |
This is one is no longer worth a consideration |
closes #1380
Feature
set_datanames
has a limited effect because of the fact that modules can have$datanames
slot set to names which are absolutely crucial for module to work. This is why we allow usingset_datanames
when$datanames == "all"
. Adding "negative selection" will also have limited effect for the same reason but the code complication seems big enough to not recommend this feature.