#1569 | Changed default value of schema.repository.deleteSchemaPathSuffix to empty string. #1754
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.
Why on earth did I change so many lines just to change the default config value?
I've noticed that there is a "hacky" constructor with default values in
SchemaRegistryRawSchemaClient
. So to change the default value ofdeleteSchemaPathSuffix
I would have to make changes in two places:After analysis, I've found out that the default constructor is used to provide schema client to
hermes-frontend
andhermes-consumers
. Those default clients didn't even use thedelete/create/validate
methods, so I've introduced an read-only abstraction to get rid of this "hacky" constructor with default values.After this change changing the
deleteSchemaPathSuffix
can be done just in one place.Additionally, the code is cleaner and the read-only schema client is simpler and uses less dependencies.
If you don't like this change I can drop the commit with the refactor.