Optional condition value

Hello,

I have some operators that doesn’t require a condition value (EXISTS, NOT EXISTS)

Could it be made optional ? I can pass value: null but would be better to just not pass it at all. 👍

[CacheControl]

@jgoux Sorry for the delayed response; I’ve been busy.

I see your point, and I think it’s a good one. There’s a couple considerations we’d need to think about and investigate before this change could be implemented:

• Developer friendliness; if a value prop is not provided, is that most likely due to programmer error (a bug)? If so, does value of allowing undefined properties outweight the cost of allowing devs to potentially shoot themselves in the foot?
• json serialization does not include undefined properties. does that matter / do we care?
• due diligence around the code itself to ensure things won’t break by allowing undefined values.

For now your best bet is to simply add those explicit nulls, which it sounds like you’ve already done.

[jgoux]

This is what I actually use to define my exists and not exists operators. The thing is I don’t need the jsonValue part, because the operator is opering only on the factValue. It’s just something like : factValue => factValue !== undefined.

So the logic would be to not have to specify a value key in the condition, but if I omit it, it raises an error about it.