[Bug]: Notification filters should use []FilterExpressions type

[hgiasac]

What's on your mind?

Currently, we are impossible to input filters with OR condition into the Notification model.

"filters": [
  {"field": "tag", "key": "level", "relation": "=", "value": "10"}, 
  {"operator": "OR"}, {"field": "tag", "key": "level", "relation": "=", "value": "20"}
]

The type of the Filters field should be []FilterExpressions.

Code of Conduct

• I agree to follow this project's Code of Conduct

[sherwinski]

Hello! Apologies that this question has gone stale.
If this question is still a current concern, please ping me and we will investigate.

[shebinleo]

@sherwinski Yes, it is. Currently, there is no way to set the operator for the filter with an OR condition in the Notification model.

[sherwinski]

@shebinleo Noted, I will confer with the team to try and get this patched in a future release.

[dreamlabsg]

For now, I was able to do a workaround provided here #27 (comment)

[sherwinski]

This has been fixed in the latest major release (https://github.com/OneSignal/onesignal-go-api/releases/tag/v5.2.0-beta1) so for anyone still running into this, I would definitely encourage upgrading library versions. Please feel free to comment here or open a new issue if there are still any questions about this.

Thanks