[CHA-0] Fix QueryReminders to use filter parameter instead of filter_conditions #190
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CLA
Description of the pull request
Changes
QueryRemindersAsyncAPI call to usefilterparameter instead offilter_conditionsUserMessageRemindersfield toChannelTypemodels for channel type configurationWhy
QueryReminders Fix
The API expects the parameter name
filter, notfilter_conditions. This fix aligns the SDK with the actual API specification.ChannelType Enhancement
The
UserMessageRemindersfield was missing from the ChannelType models, which meant it was impossible to enable message reminders at the channel type level usingUpdateChannelTypeAsync().While reminders could be enabled per-channel via
config_overrides, there was no way to set it as default for all channels of a specific type..NET Usage After Fix
Testing