Add support for config-driven channel overrides :gz and :null#1069
Conversation
Accepted is also ':' which would cancel hard-coded modifiers in the code.
|
@tajgr can se set some milestone/deadline for go or not to go? My motivation is to release OSGAR 1.1 and this could be new feature (while in case of problems users still can fallback to 1.0.0) |
|
Ok, that takes sense. This week? This feature should be also added to the documentations. |
Take your time - this or next week is fine, but I would like to close it before "Dobyvani hradu 2026". Regarding parameters - in my opinion the driver itself should provide the best reasonable parameters. For example to publish depth without gzip is total non-sense, and I would like to avoid cases when "I forgot". So hard-coded would be recommended parameters, which you can override in JSON. You are right, that I should remove also the duplicity in some drivers where the gzip is hacked with extra (non-standard) way, which I am trying to remove by this PR. Regarding documentation, Elena added some notes - let me know if you would like to see more. |
Accepted is also ':' which would cancel hard-coded modifiers in the code.
(as described in the email, but maybe code is more clear)