Skip to main content

Command Palette

Search for a command to run...

Kotlin Code Smell 8 - Too Many Arguments

Optimizing Function Design: The Art of Grouping and Simplifying Arguments

Published
2 min read
Kotlin Code Smell 8 - Too Many Arguments
Y

I've started to work as a software engineer at 2014, however, I started to write code at high-school.

My first language was Assembly, but still, I fall in love with the possibilities to make the computer to do as you wish, shortly after that I started to write in C.

Later on I studied a practical engineering in electricity, and during this time discovered that I preferred much more writing code than design electrical components.

As a result of this understanding I decided to switch and study bachelor degree in computer science in Reichman university, where the focus was of the Java language.

Today I'm working at SumUp using Kotlin, SpringBoot & Micronaut, Cassandra and Kafka

TL;DR: Avoid passing more than three arguments to your functions.

Problems

  • Low maintainability.

  • Low reusability.

  • Coupling.

  • Readability.

Solutions

  • Identify cohesive relationships among arguments.

  • Create a "context" or related group.

  • Consider using the Method Object Pattern.

  • Avoid using "basic" types such as strings, arrays, and integers, and instead think in terms of objects.

Exceptions

  • Operations in the real world that do not require cohesive collaborators.

Sample Code

Wrong

class Printer {
    fun print(
        documentToPrint: String,
        paperSize: String,
        orientation: String,
        grayScales: Boolean,
        pageFrom: Int,
        pageTo: Int,
        copies: Int,
        marginLeft: Float,
        marginRight: Float,
        marginTop: Float,
        marginBottom: Float
    ): Unit = TODO()
}

Right

class PaperSize {
    //...
}

class Document {
    //...
}

class PrintMargins {
    //...
}

class PrintRange {
    //...
}

class ColorConfiguration {
    //...
}

class PrintOrientation {
    //...
}

class PrintSetup(
    paperSize: PaperSize,
    orientation: PrintOrientation,
    color: ColorConfiguration,
    range: PrintRange,
    copiesCount: Int,
    margins: PrintMargins
)

class Printer {
    fun print(
        documentToPrint: Document,
        setup: PrintSetup
    ): Unit = TODO()
}

Conclusion

To improve code quality, identify and group related arguments. Aim for real-world mappings and cohesive objects.

If a function requires too many arguments, some of them might be better suited for class construction. This is also a design issue.

More Info

Credits

Kotlin Code Smells

Part 29 of 36

In this series, we will see several symptoms and situations that make us doubt the quality of our development. We will present possible solutions. Most are just clues. They are no hard rules.

Up next

Kotlin Code Smell 7 - Long Chains Of Collaborations

Decoupling Collaborations: Ensuring Code Stability through Reduced Chains and Better Encapsulation

More from this blog

Yonatan Karp-Rudin | kotlin for backend developer skills | java for backend developer skills | SpringBoot | Tutorials

57 posts

Experienced Senior Software Engineer passionate about functional programming & Kotlin. Excels in app development, optimization, and team collaboration. Let's create something amazing!