Make config type, variant names less confusing #1327
Merged
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.
Motivation
I want to add a kafka variant to
SenderConfig
andReceiverOut
, but with current variant names, that will either cause a common suffix (which clippy will likely complain about) or odd-looking naming inconsistencies.Solution
Remove the unnecessary
Consumer
,Producer
variant name suffixes. Since both enums are#[serde(untagged)]
, this does not affect deserialization. Also renameQueueConsumerConfig
toQueueSenderConfig
, which seems to be correct naming given it contains fields of typeSender*Opts
and it's contained in the only variant ofSenderConfig
, whereas the previous name was rather confusing.Part of https://github.com/svix/monorepo-private/issues/8508.