feat: Add warning for nonexistent query conditions #155
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When querying for data using
EEGDashDataset, if a user provides afilter value that does not exist in the dataset (e.g., a misspelled
task name), the class would previously return an empty or incomplete
dataset without any notification. This could lead to user confusion.
This change introduces a warning mechanism that checks the user's query
conditions against the fetched records. If any of the requested values
for a given field do not match any records, a warning is logged to
inform the user.
This is implemented by:
EEGDashDataset.__init__method to fetch recordsbefore creating the dataset objects.
_warn_for_unmatched_query_conditionsmethod to performthe validation.
tests/test_warnings.pyto verify thenew warning functionality under various conditions.
PR created automatically by Jules for task 12458885612927622774