seeseemelk/MockBukkit

View on GitHub
src/main/java/be/seeseemelk/mockbukkit/ServerMock.java

Summary

Maintainability
A
2 hrs
Test Coverage

Method createPotionEffectTypes has 40 lines of code (exceeds 25 allowed). Consider refactoring.
Open

    private void createPotionEffectTypes()
    {
        for (PotionEffectType type : PotionEffectType.values())
        {
            // We probably already registered all Potion Effects
Severity: Minor
Found in src/main/java/be/seeseemelk/mockbukkit/ServerMock.java - About 1 hr to fix

    Method getPlayer has a Cognitive Complexity of 7 (exceeds 5 allowed). Consider refactoring.
    Open

        @Override
        public Player getPlayer(String name)
        {
            Player player = getPlayerExact(name);
            if (player != null)
    Severity: Minor
    Found in src/main/java/be/seeseemelk/mockbukkit/ServerMock.java - About 35 mins to fix

    Cognitive Complexity

    Cognitive Complexity is a measure of how difficult a unit of code is to intuitively understand. Unlike Cyclomatic Complexity, which determines how difficult your code will be to test, Cognitive Complexity tells you how difficult your code will be to read and comprehend.

    A method's cognitive complexity is based on a few simple rules:

    • Code is not considered more complex when it uses shorthand that the language provides for collapsing multiple statements into one
    • Code is considered more complex for each "break in the linear flow of the code"
    • Code is considered more complex when "flow breaking structures are nested"

    Further reading

    Remove this unused method parameter "title".
    Open

        public InventoryMock createInventory(InventoryHolder owner, InventoryType type, String title, int size)

    Unused parameters are misleading. Whatever the values passed to such parameters, the behavior will be the same.

    Noncompliant Code Example

    void doSomething(int a, int b) {     // "b" is unused
      compute(a);
    }
    

    Compliant Solution

    void doSomething(int a) {
      compute(a);
    }
    

    Exceptions

    The rule will not raise issues for unused parameters:

    • that are annotated with @javax.enterprise.event.Observes
    • in overrides and implementation methods
    • in interface default methods
    • in non-private methods that only throw or that have empty bodies
    • in annotated methods, unless the annotation is @SuppressWarning("unchecked") or @SuppressWarning("rawtypes"), in which case the annotation will be ignored
    • in overridable methods (non-final, or not member of a final class, non-static, non-private), if the parameter is documented with a proper javadoc.
    @Override
    void doSomething(int a, int b) {     // no issue reported on b
      compute(a);
    }
    
    public void foo(String s) {
      // designed to be extended but noop in standard case
    }
    
    protected void bar(String s) {
      //open-closed principle
    }
    
    public void qix(String s) {
      throw new UnsupportedOperationException("This method should be implemented in subclasses");
    }
    
    /**
     * @param s This string may be use for further computation in overriding classes
     */
    protected void foobar(int a, String s) { // no issue, method is overridable and unused parameter has proper javadoc
      compute(a);
    }
    

    See

    • CERT, MSC12-C. - Detect and remove code that has no effect or is never executed

    There are no issues that match your filters.

    Category
    Status