Handling param differences when using on-demand collections?

[Nick-Motion]

I'm using useLiveQuery with on-demand collections where the API and client need to filter on the same logical field, but using different fields/logic. Wondering how to do this in a non-hacky way.

Current approach:

// 1. Pass to API via marker (always true locally due to eq(1,1))
conditions.push(
  or(eq(1, 1), eq((todos as any).assignedToMe, true))
)

// 2. Actual client-side filtering with different logic
query = query.fn.where((row) => row.todos.assigneeId === currentUserId)

The problem is there is no assignedToMe field - but that's the API param name.

The or(eq(1, 1), ...) is a hack to pass the field into queryFn loadSubsetOptions, where it is passed in the call.

I have quite a few other cases on the same general theme as well - for example, API expects a string param, which corresponds to a deep field within the model:

// 1. Pass to API via marker (always true locally due to eq(1,1))
conditions.push(
  or(eq(1, 1), eq(todos.labelId, labelId))
)

// 2. Actual client-side filtering with different logic
query = query.fn.where((row) =>
  row.todos.labels?.some((label) => label.id === labelId && label.active) ?? false
)

Is there a cleaner way to express "send this to the API, but use different logic locally"?

Thank you!