in operator does not seem to work whereas is does

[ole-magnus]

Using the filter options is, in, etc, I run into problems:

const entitlements = await this.chargebee?.entitlement
  .list({
    feature_id: { is: featureId },
    entity_type: { in: ['plan_price'] },
  })
  .request();

does not work (the request fails)

whereas

const entitlements = await this.chargebee?.entitlement
  .list({
    feature_id: { is: featureId }
  })
  .request();

does.

This just follows the suggested typings and approach from the API documentation.

It would be great if someone from Chargebee could comment both on these issues but also look into the open PRs and other issues that seem unaddressed.

This issue from 2022 seems related and it worries me there are no responses: #31

[cb-sriramthiagarajan]

Hi @ole-magnus, I'm sorry for the inconvenience. We're currently looking into this and will get back soon. Though it looks similar, #31 is probably a different issue which is related to custom field and we'll address that as well.

[ole-magnus]

@cb-sriramthiagarajan ok, thanks for the response. Do you have a timeline on this?

[cb-sriramthiagarajan]

Hi @ole-magnus, we're currently looking into this. I'll come back with an update latest by tomorrow. Thanks for your patience.

[cb-sriramthiagarajan]

Hi @ole-magnus, we've identified the issue and will be working on a fix. I see that there's a support ticket open for this and we'll be following up there.

Will keep this issue open until it's fixed.

[ole-magnus]

@cb-sriramthiagarajan What is happening here? Anyone working on it? What is the ETA?

[cb-sriramthiagarajan]

Yes @ole-magnus, we're working on this. Unfortunately I don't have an ETA at the moment. I'll come back with an update later this week.

[cb-sriramthiagarajan]

Hi @ole-magnus, we're still working on this. Will keep this issue posted once we have a timeline. Thanks for your patience.