[Improvement] Optimize return value type for table service interface#208
Merged
SteNicholas merged 1 commit intoapache:mainfrom May 5, 2024
Merged
Conversation
SteNicholas
changed the title
SteNicholas
pushed a commit
that referenced
this pull request
May 5, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Relates to: #205
Purpose
This pull request aims to align the return types of our service layer interfaces with standard Spring framework practices by removing the use of a custom response wrapper (R). This change simplifies our service layer, ensuring it focuses solely on business logic and remains agnostic of HTTP response structures, as discussed in Issue #205.