Plugin-based architecture?

[ankushg]

This project is super cool!

I'm curious if you'd explore a plugin-based architecture.

As an example, we have enums declared like:

enum class MyEnum(val value: String) {
  OPTION_A("option_a"),
  OPTION_B("option_b");
}

We'd love to write a custom rule that lets us export MyEnum as the underlying value (as a lightweight String), rather than a heavier class.

We also have other enum classes that use Ints.

[glureau]

Thanks!

That was my first intention, but not sure how to setup a plugin-based architecture with KSP, but it could be interesting. If you know another project using this architecture with KMP I'm interested.

For the enum case, I don't think there is a lot of way to encode it: String, Int, or fully wrapped may be enough. I was thinking at an ExportMode in the annotation, something like that: #5

And it'll warn if there is a public method or field exposed as it cannot be exported in those modes for example. Is it matching your needs?

[glureau]

I tried many solutions but all were very limited, and eventually just a subset of what KSP offers.

I think that KSP already provides a "plugin-based architecture" in the sense that you could write your own KSP processor with your custom annotation, and use this annotation on the enums you want to generate differently for example. Given you respect the contract (2 methods import/export + expected package name) then it'll work with the other classes KustomExport is currently generating. So I'm closing this ticket for now.

Indeed, do not hesitate to re-open if you have a more specific need/approach on this topic.