Skip to content
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

JBIDE-25855 - move publish controller to API #568

Merged
merged 1 commit into from Mar 29, 2018

Conversation

robstryker
Copy link
Member

Signed-off-by: Rob Stryker rob@oxbeef.net

Signed-off-by: Rob Stryker <rob@oxbeef.net>
@rhdevelopers-ci
Copy link

SonarQube analysis reported 11 issues

  • CRITICAL 4 critical
  • MAJOR 3 major
  • MINOR 3 minor
  • INFO 1 info

Top 10 issues

  1. CRITICAL StandardFileSystemPublishController.java#L298: Refactor this method to reduce its Cognitive Complexity from 27 to the 15 allowed. rule
  2. CRITICAL StandardFileSystemPublishController.java#L519: Refactor this method to reduce its Cognitive Complexity from 37 to the 15 allowed. rule
  3. CRITICAL StandardFileSystemPublishController.java#L776: Refactor this method to reduce its Cognitive Complexity from 19 to the 15 allowed. rule
  4. CRITICAL StandardFileSystemPublishController.java#L21: Rename this class. rule
  5. MAJOR StandardFileSystemPublishController.java#L331: Rename "publishType" which hides the field declared at line 132. rule
  6. MAJOR StandardFileSystemPublishController.java#L571: Remove this useless assignment to local variable "error". rule
  7. MAJOR StandardFileSystemPublishController.java#L21: Add the missing @deprecated annotation. rule
  8. MINOR StandardFileSystemPublishController.java#L571: Remove this unused "error" local variable. rule
  9. MINOR StandardFileSystemPublishController.java#L621: Remove this use of "ServerLogger"; it is deprecated. rule
  10. MINOR StandardFileSystemPublishController.java#L820: Immediately return this expression instead of assigning it to the temporary variable "deltas". rule

@adietish
Copy link
Member

adietish commented Mar 29, 2018

@robstryker I'm fine with this change. Questions remain: don't we need to bump the version? I ack that your solution keeps the class in place extending the API version of it, which ensures no consumer gets broken. +1 for that.

@robstryker
Copy link
Member Author

Version was bumped when 4.5.3 stream began. No need for more bumping.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants