A modern programming language that makes developers happier.

kotlinlang

About 3rd party types, actually this is just not documented yet, but it's already possible through a KSP plugin option! You just have to provide a list of FQCN <https://github.com/nesk/akkurate/blob/c126968746f3270596d15afbfdf69ede9bacf165/plugin/src/main/kotlin/dev/nesk/akkurate/ksp/ValidateAnnotationProcessorConfig.kt#L31-L42|to the validatableClasses option.>

Lets say I write (in my test module):
```@Validate
data class Fixture(val foo: Foo, val baz: Baz)```
will the ksp plugin generate accessors for Foo and Baz (from the main module), even though ksp is only enabled in the test module, since it has to generate for `Fixture` anyways?

No, you will only have accessors generated for `Fixture`
The reason I did not do this is to avoid generating to much accessors without the developer being aware of this, I don't want this to snowball. Maybe I will change this behavior in the future, nothing is settled.

I'd understand that reasoning, but just as long as you don't generate double accessors (for classes already annotated + transitive), you could always provide an expiremental `@Validate(generateTransitive=true)` or something similar, that way it's only opt-in.

I will think about it! But, couldn't the `validatableClasses` option do the trick in your case? It also avoids creating a dummy `Fixture` class.

It could, but it's a bit cumbersome to have to provide a very big list of FQCNs...

`internal var validatablePackages: Set&lt;String&gt; = emptySet()` is not yet implemented I suppose?

its implemented… privately :sweat_smile:

the reason is simple: it uses an experimental feature of KSP

you can use it at your own risk: <https://github.com/nesk/akkurate/blob/c126968746f3270596d15afbfdf69ede9bacf165/library/build.gradle.kts#L47>

Btw, how do I set that property? Using the `ksp { arg("???", "????" }` block in build.gradle.kts? How would I separate the list of packages, one humongous string?

yes, use the `ksp { arg(...) }` block, you can write something like that:

```ksp {
    arg("validatableClasses", "org.example.Foo|org.example.Bar")
}```
Unfortunately, ksp plugins only accept strings as option values, so have to use a "humongous string" like you said :sweat_smile:, each class separated by a `|`

You can improve the readability by joining multiple strings into one:

```listOf("org.example.Foo", "org.example.Bar").joinToString("|")```
