macgregor/alexandria

View on GitHub
alexandria-core/src/main/java/com/github/macgregor/alexandria/AlexandriaSync.java

Summary

Maintainability
B
4 hrs
Test Coverage

Method sync has 49 lines of code (exceeds 25 allowed). Consider refactoring.
Open

    protected void sync() throws AlexandriaException {
        BatchProcess<Config.DocumentMetadata> batchProcess = new BatchProcess<>(context);
        batchProcess.execute(context -> context.config().metadata().get(), (context, metadata) -> {
            log.debug(String.format("Syncing %s with remote.", metadata.sourceFileName()));
            remote.validateDocumentMetadata(metadata);

    Rename "context" which hides the field declared at line 30.
    Open

            batchProcess.execute(context -> context.config().metadata().get(), (context, metadata) -> {

    Overriding or shadowing a variable declared in an outer scope can strongly impact the readability, and therefore the maintainability, of a piece of code. Further, it could lead maintainers to introduce bugs because they think they're using one variable but are really using another.

    Noncompliant Code Example

    class Foo {
      public int myField;
    
      public void doSomething() {
        int myField = 0;
        ...
      }
    }
    

    See

    Rename "context" which hides the field declared at line 30.
    Open

            }, (context, exceptions) -> {

    Overriding or shadowing a variable declared in an outer scope can strongly impact the readability, and therefore the maintainability, of a piece of code. Further, it could lead maintainers to introduce bugs because they think they're using one variable but are really using another.

    Noncompliant Code Example

    class Foo {
      public int myField;
    
      public void doSomething() {
        int myField = 0;
        ...
      }
    }
    

    See

    Rename "context" which hides the field declared at line 30.
    Open

            batchProcess.execute(context -> context.config().metadata().get(), (context, metadata) -> {

    Overriding or shadowing a variable declared in an outer scope can strongly impact the readability, and therefore the maintainability, of a piece of code. Further, it could lead maintainers to introduce bugs because they think they're using one variable but are really using another.

    Noncompliant Code Example

    class Foo {
      public int myField;
    
      public void doSomething() {
        int myField = 0;
        ...
      }
    }
    

    See

    Add a default case to this switch.
    Open

                switch(state){

    The requirement for a final default clause is defensive programming. The clause should either take appropriate action, or contain a suitable comment as to why no action is taken.

    Noncompliant Code Example

    switch (param) {  //missing default clause
      case 0:
        doSomething();
        break;
      case 1:
        doSomethingElse();
        break;
    }
    
    switch (param) {
      default: // default clause should be the last one
        error();
        break;
      case 0:
        doSomething();
        break;
      case 1:
        doSomethingElse();
        break;
    }
    

    Compliant Solution

    switch (param) {
      case 0:
        doSomething();
        break;
      case 1:
        doSomethingElse();
        break;
      default:
        error();
        break;
    }
    

    Exceptions

    If the switch parameter is an Enum and if all the constants of this enum are used in the case statements, then no default clause is expected.

    Example:

    public enum Day {
        SUNDAY, MONDAY
    }
    ...
    switch(day) {
      case SUNDAY:
        doSomething();
        break;
      case MONDAY:
        doSomethingElse();
        break;
    }
    

    See

    Similar blocks of code found in 2 locations. Consider refactoring.
    Open

                    case CREATE:
                        if(Resources.fileContentsAreBlank(metadata.sourcePath().toString())){
                            log.info(String.format("%s has no contents, not creating on remote", metadata.sourceFileName()));
                        } else{
                            remote.create(metadata);
    alexandria-core/src/main/java/com/github/macgregor/alexandria/AlexandriaSync.java on lines 132..141

    Duplicated Code

    Duplicated code can lead to software that is hard to understand and difficult to change. The Don't Repeat Yourself (DRY) principle states:

    Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.

    When you violate DRY, bugs and maintenance problems are sure to follow. Duplicated code has a tendency to both continue to replicate and also to diverge (leaving bugs as two similar implementations differ in subtle ways).

    Tuning

    This issue has a mass of 98.

    We set useful threshold defaults for the languages we support but you may want to adjust these settings based on your project guidelines.

    The threshold configuration represents the minimum mass a code block must have to be analyzed for duplication. The lower the threshold, the more fine-grained the comparison.

    If the engine is too easily reporting duplication, try raising the threshold. If you suspect that the engine isn't catching enough duplication, try lowering the threshold. The best setting tends to differ from language to language.

    See codeclimate-duplication's documentation for more information about tuning the mass threshold in your .codeclimate.yml.

    Refactorings

    Further Reading

    Similar blocks of code found in 2 locations. Consider refactoring.
    Open

                    case UPDATE:
                        if(Resources.fileContentsAreBlank(metadata.sourcePath().toString())){
                            log.info(String.format("%s has no contents, not updating on remote", metadata.sourceFileName()));
                        } else {
                            remote.update(metadata);
    alexandria-core/src/main/java/com/github/macgregor/alexandria/AlexandriaSync.java on lines 122..131

    Duplicated Code

    Duplicated code can lead to software that is hard to understand and difficult to change. The Don't Repeat Yourself (DRY) principle states:

    Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.

    When you violate DRY, bugs and maintenance problems are sure to follow. Duplicated code has a tendency to both continue to replicate and also to diverge (leaving bugs as two similar implementations differ in subtle ways).

    Tuning

    This issue has a mass of 98.

    We set useful threshold defaults for the languages we support but you may want to adjust these settings based on your project guidelines.

    The threshold configuration represents the minimum mass a code block must have to be analyzed for duplication. The lower the threshold, the more fine-grained the comparison.

    If the engine is too easily reporting duplication, try raising the threshold. If you suspect that the engine isn't catching enough duplication, try lowering the threshold. The best setting tends to differ from language to language.

    See codeclimate-duplication's documentation for more information about tuning the mass threshold in your .codeclimate.yml.

    Refactorings

    Further Reading

    There are no issues that match your filters.

    Category
    Status