fix: Fix conversion of Kafka ConfigEntry object to it's corresponding Vertx Kafka client object #287
+150
−1
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:
ConfigEntry
class creates objects by only initializing thename
andvalue
fields. This means that when an object of this class is created to represent a Kafka ConfigEntry object, the properties such asConfigSource
,isSensitive
,isReadOnly
andConfigSynonym
of the Kafka object are never mapped to the new object.Description:
ConfigEntry
class which initializes these additional fields along withname
andvalue
fields. The new constructor shares a lot of similarities with this constructor in order to keep this class aligned with its Kafka counterpart.ConfigEntry
objects to objects of the aboveConfigEntry
class.Closes #285