Fix/update imperative controller #323
Open
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.
MonoResponseEntityCreatorinstead ofCreateResponseEntityCreatorsince we usually return null or a response class when updatingNullServiceResponseclass to be used for all cases where a null response is preferred as a possible return value.Rather than return
nulldirectly, users can utilize this class and returnNullServiceResponse.INSTANCE(which returns null) instead as it also implementsBaseServiceResponseadhering to the generic parameter contract set in all our controllers.DISCUSSION: Is there another name that would fit better than just
NullServiceResponse? (keeping in mind our use case would be that we want to returnnullas a value?