Skip to content

[FIX] Handle "order" in note_keys #36

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.

Sign up for GitHub

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

Merged
jdkent merged 1 commit into from
Dec 4, 2025
Merged

[FIX] Handle "order" in note_keys #36

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions compose_runner/run.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -198,6 +198,10 @@ def apply_filter(self, studyset, annotation):
weights = self.cached_specification.get("weights", [])
weight_conditions = {w: c for c, w in zip(conditions, weights)}

# since we added "order" to annotations
if isinstance(column_type, dict):
column_type = column_type.get("type")

if not (conditions or weights) and column_type != "boolean":
raise ValueError(
f"Column type {column_type} requires a conditions and weights."
Expand Down