Use serialization-properties over AbstractDecoder.

[corrado4eyes]

#412

[codecov]

Codecov Report

Attention: Patch coverage is 57.14286% with 3 lines in your changes missing coverage. Please review.

Project coverage is 80.68%. Comparing base (1df1263) to head (7ee15a9).
Report is 1391 commits behind head on develop.

Files with missing lines	Patch %	Lines
...plendo/kaluga/links/manager/DefaultLinksManager.kt	50.00%	3 Missing ⚠️

Additional details and impacted files

@@              Coverage Diff              @@
##             develop     #403      +/-   ##
=============================================
+ Coverage      80.59%   80.68%   +0.08%     
- Complexity       254      259       +5     
=============================================
  Files            674      673       -1     
  Lines           8868     8842      -26     
  Branches         746      743       -3     
=============================================
- Hits            7147     7134      -13     
+ Misses          1534     1523      -11     
+ Partials         187      185       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[dasdranagon]

Looks good! I would consider some improvements. in tests also would always recommend starting with the simplest test cases.
Check my comment (you can resolve it after reading)

[dasdranagon]

FYI: #61 is resolved and has nothing to do with this PR ;)

[posytive]

Nice work! I don't see anything wrong with the additions you made and the overall implementation of this feature.
In this sense, it can be merged after you make the Readme a bit more clear

But I keep thinking that there are too many limitations for a developer using this module, and in the sense we should consider a refactor.
Specifically, I think is better to avoid:

• forcing an order of params in the query
• passing nulls explicitely
• passing the size of a list

In the first 2 cases, consider using Serialization modules that do this for us automatically (even if we need to map the data un-efficiently at the beginning, queries are not so long): the good old kotlinx.serialization.json or kotlinx.serialization.properties
The latter seems exactly what you need

[corrado4eyes]

You can do

""" 
    foo
    bar 
""".trimIndent().lines().joinToString("")

It would work only for white spaces before foo and after bar and not what is in the middle let's say \t\t baz

[thoutbeckers]

@corrado4eyes https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.text/trim-indent.html does exactly what @avdyushin says