[Improve] Improve streampark-console method name base on [3.1 Naming Style] #3364
Conversation
This file contains 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
…[3.1 Naming Style]
caicancai
reviewed
Nov 28, 2023
| @@ -118,7 +118,7 @@ public RestResponse get(String id) throws InternalException { | |||
| @Operation(summary = "List the applications sql histories") | |||
| @PostMapping("history") | |||
| public RestResponse sqlhistory(Application application) { | |||
| List<FlinkSql> sqlList = flinkSqlService.history(application); | |||
| List<FlinkSql> sqlList = flinkSqlService.listFlinkSqlHistory(application); | |||
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changes were proposed in this pull request
Issue Number: see #3064
Brief change log
Improve streampark-console system package module service name base on [3.1 Naming Style]
Just method name
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Yes
This change is already covered by existing tests, such as (please describe tests).
No
This change added tests and can be verified as follows:
Does this pull request potentially affect one of the following parts