Thanks for the detailed review.

I generally prefer leaving customization points open (especially for libraries), so I initially planned to add a custom option and did think about Gradle configuration/cache implications. That said, I agree that exposing this level of flexibility in the Gradle DSL may not be worth the added complexity, and it could also be a maintenance burden. I’ll align with your philosophy as the maintainer and revise the implementation based on your feedback.

For context, as mentioned in the original issue, I’m currently using this only via the Gradle plugin path, so my perspective may not fully match the project-wide point of view. Your review was helpful in that regard as well.

At the beginning of my contribution on avro4k, I've been opening a lot the customisation. But this became much more complex to maintain, as any new feature can quickly be against previously open customization.

Now I'm more YAGNI : You Ain't Gona Need It, until I or someone really needs it.

Lets continue the discussion on your actual need in the issue 👌

Just for you to know, I've merged many PRs.

Basically, the main changes for you are:

• Avro4kPluginSourcesGenerationExtension has been moved to its own file
• you can add schemas with -fail at the end to test failing scenarios in kotlin-generator

LOL — I didn’t realize “Add suggestion to batch” was for committing them all at once. I thought it was something like CI-related, so I applied each suggestion individually. Turns out I could’ve done it in one go.

Thanks for the feedback! I really enjoyed working on this PR—it was a great experience