-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Edit topic with advanced configs #1414
Conversation
Signed-off-by: muralibasani <[email protected]>
Signed-off-by: muralibasani <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good
topicInfo.setAdvancedTopicConfiguration( | ||
topicConfigurationRequest.getAdvancedTopicConfiguration()); | ||
} catch (JsonProcessingException e) { | ||
throw new RuntimeException(e); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be worth creating a KlawException that is caught in the controller advice that returns a bad request with a message per processable advanced config.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good one. updated, but now suppressing that error. what do you think.
Signed-off-by: muralibasani <[email protected]>
About this change - What it does
Resolves: #1392
Why this way
Edit topic requests now can handle other configs