Open Zambito1 opened 4 months ago
If it is a model option - as the configs for consumer/stream then they match the model - because it is sent as is to the server. On client API options it uses camel case - I will revisit for the 3.0 release I am working on as this would be an API change, but for certain it should be consistent.
Observed behavior
This is the only field on the object that does not use snake case. It also does not match the nearly identical ConsumerConfig object, which has a field named
filter_subjects
as well asfilter_subject
. I switched from using the Jetstream Manager API to the Jetstream Client API, and this difference tripped me up, as my undefinedfilterSubjects
field led to my filter being ignored.Expected behavior
Consistent casing
Server and client version
Library version v1.27.0
Host environment
N/A
Steps to reproduce
N/A