Looking for some feedback on how to handle repeated annotations in XProcessing (but relevant to any user of KSP). (in thread)

Hi there, can someone help me confirm this this is an issue or we are using it wrong? https://github.com/google/ksp/issues/351

getSymbolsWithAnnotation

seems not to pick up annotation used in function/constructors parameters. Basically this works:

class MyClass(@Builder val param: String)

but this doesn’t:

class MyClass(@Builder param: String)

inDepth

seems to have no effect either 🤔

Apologies if this question isn’t appropriate to KSP, as my understanding of it is quite small. Let’s say I have several classes that inherit from an interface throughout my project, and would like to create some kind of output (CSV or so, not to be used in the project) that looks at all implementations of that interface together with its properties (e.g. a Map with simple types/enums). Would it be possible with KSP to do such a thing? Or should I look for a fully fledged compiler plugin?

lemme know if you want me to file a GH issue, or if this is a KI already

Hi, here is the latest KSP bi-weekly release: Highlights • Multiplatform is back working again for JVM platform. • Corresponding Kotlin version is bumped to 1.4.31. This release still works with 1.4.30. To mute the version mismatch warning when using with Kotlin-1.4.30, use 

-Pksp.version.check=false

. • Supported Gradle 7.0-rc-1. API / behavior changes • Use-site annotations are now attached to use-sites consistently. Previously, they are attached to where they were declared if the source is available, and the use-sites if the source isn't available. As always, please give it a try and let us know what you think, especially on the API design!

Hello everyone! Iam receiving an error when calling

KSName.asString()

. What is strange is that I had a working version of my processor but after a few changes in the project structure (moved classes do different packages and so on) this error is now happening. I am basically trying to get the qualified name or the simple name of a Kotlin annotation class. Basically this is the code:

annotation as KSAnnotation
val declaration = annotation.annotationType.resolve().declaration
val qualifiedName = (declaration.qualifiedName ?: declaration.simpleName).asString()

val className = ClassName.bestGuess(qualifiedName)

If I print

declaration

I can already see the string “Error type synthetic declaration”

Guys, I am struggling on making my processor incremental. I am receiving some exceptions when modifying a dependency, sometimes it’s a NPE, sometimes it’s an ArrayOutOfBounds, but if I re-run everything executes just fine. I already tried to create the

Dependencies

instance by just adding the

symbol.containingFile

and also tried by adding all the files of the inherited interfaces. For more context, I am generating classes base on an annotated interface which can then inherit from other interfaces.

Hello! I am exploring KSP to write a compiler plugin, something like Parcelize, so it would implement a predefined interface for annotated classes. Like you have a data class that implements the interface but you don't write the actual implementation code. And then you annotate the class with a marker annotation and the plugin should add the implementation. Is it a doable task for KSP?

Can someone explain the change

KSP now handles annotation use site targets internally for property accessors (namely

@get:Anno

,

@set:Anno

).

property accessors will have corresponding targeted annotations from their receiver properties

annotations with

@get:

and

@set:

targets will not appear in property's annotation list.

I had this code to find a getter annotation on a constructor val and it's no longer finding it

class Foo(@get:Annotation val bar: String)

fun KSAnnotated.hasAnnotation(className: String, useSiteTarget: AnnotationUseSiteTarget? = null): Boolean {
    return annotations.any {
        it.annotationType.resolve().declaration.qualifiedName?.asString() == className &&
            useSiteTarget == it.useSiteTarget
    }
}

override fun hasAnnotation(className: String): Boolean {
    return declaration.getter?.hasAnnotation(className) == true ||
                declaration.hasAnnotation(className, AnnotationUseSiteTarget.GET)
}

Hello everyone! I’m am trying to improve my processor and I am struggling to get the

typeParameters

from this

object

I tried a few things already but without success.

object SchemeProperty : ValueModifier<String, String>{ ... }

Hi, here is the latest KSP release: Highlights • Updated Kotlin version to 1.4.32 • Added 

Resolver.getDeclarationsFromPackage()

 API, this API is to retrieve declarations with a given package name from both classpath and sources. Note that this API can be expensive. • Bug fixes around generic type arguments and jvm_static detection. Please take a try and let us know if you have any comments!

Hi everyone! I have a multi-module/libraries Android Kotlin project and would like to check the uniqueness of ID's across module/libraries boundaries. The ID's have the following code structure:

@ErrorID val errorID = 0xA03L

Is it possible to implement such a requirement with ksp or would it require building a Kotlin compiler plugin?

getting this error on an incremental build, I assume this is a bug? What info would be helpful here?

Hi just wrote my first KSP processor and all works as expected. I create two files based of one source file. I took more or less the code from the ksp_sample playground. But when i compile it without clean before i get often this error:

e: java.io.IOException: No such file or directory
	at java.base/java.io.UnixFileSystem.createFileExclusively(Native Method)
	at java.base/java.io.File.createNewFile(File.java:1026)

Full backstack in Thread. When i delete the "generated/ksp" folder it compiles. Source code of my processor: https://gitlab.com/compose1/livecomposable/-/blob/develop/hotreload_ksp_processor/[…]in/kotlin/de/appsonair/compose/processor/hotreload_processor.kt

Heads up @yigit I started working on support in room compiler processing for an abstraction for KSP’s new

Resolver.getDeclarationsFromPackage()

and javac’s

Elements.getPackageElement

Doesn’t seem like it should be too hard. I created a ticket https://issuetracker.google.com/issues/185609823

XProcessing top level constructs thread. cc: @gabrielfv @elihart

Checking in on KSP and multiplatform. I'm aware that the compiler plugin itself is JVM-only at least until 1.5.20 due to lack of AnalysisHandlerExtension support on other platforms. I've also seen some stuff around making sure the KSP plugin works for JVM targets of multiplatform projects, but I don't know how well-supported that's expected to be. I can't get any multiplatform project to build that applies the KSP plugin and includes an Android target. I also am having trouble with projects including native targets if I actually wire up a ksp dependency on the JVM target. Are these issues known/expected since multiplatform support isn't ready yet?

Hi there, we have made another bi-weekly release that 1. Introduced

SymbolProcessorProvider

to get rid of the need of saving logger, options, CodeGenerator, etc in

SymbolProcessor.init()

, which will be deprecated in the future. To use the new entry point, you'll need to register

SymbolProcessorProvider

rather than

SymbolProcessor

in the service file. Please find more details in the release note. Thank you @edrd for the PR! 2. Introduced

getFunctionDeclarationByName

and

getPropertyDeclarationByName

3. Fixed a few issues around incremental processing and multiple-round. As always, please give it a try and let us know what you think!

In trying to update to alpha08, I'm seeing a crash in KSP and not sure if it's an issue in my tests or something I should file. Let me know if this seems familiar - https://github.com/ZacSweers/MoshiX/pull/107

Is

1.5.0-alpha09

rolled out? I get mixed messages from my build about whether it exists on central and the github release doesn't look intentional/filled out

KSP quickstart says that we should implement SymbolProcessorProvider to provide our processor, but all examples I found until now don't do this. Why is it so? For example: https://github.com/google/ksp/tree/8a8d16855c23f3cc24d05218b16f6c6e46fdbbd8/integr[…]/src/test/resources/on-error/on-error-processor/src/main/kotlin This project has two processors, but not processor provider.

Is it possible to use KSP on non-JVM source sets in a multiplatform project, even if compilation will fail? Say you have a non-JVM target and you are interested in analyzing the source code, without code generation. For example, count how many functions have the

@Function

annotation. May be a weird idea but what I'm thinking is: • add a fake JVM target which reads the non-JVM source set • run KSP on this target, count

@Function

s or any other read-only symbol operation • have compilation fail, we don't care because it's a fake target Would this be possible? I'm not sure if KSP gets a chance to run if the source set is not compilable (it has non-JVM imports, non-JVM dependencies...)

Hi there, hope you are enjoying Kotlin 1.5.0 already 🙂 Here is the corresponding KSP 1.5.0-1.0.0-alpha09. Nothing major has changed besides keeping up to Kotlin 1.5; More features / fixes will be in the release next week.

I was trying to add typealias support to Room XProcessing and hit an interesting case. Should there be a similar

getClassDeclarationByName

that supports

KSTypeAlias

. I'm honestly not sure what is the right behavior here. I think in XProcessing, we'll just resolve them immediately as we wrap which might cause some confusion but will work fine (except for the fact that generated code would access the resolved type rather than type alias). But i don't know if there are other cases where processors would need to find classes by type alias

Hi, we are working on changing most of our API return type from

Collection

to

Sequence

for a better performance. This change will need your attention as

Sequence

is lazily evaluated and requires a terminal operation to make it actually compute. Here is my API change, please kindly take a look and leave comments in case of any concerns. The most important item I want to hear from you is if your use case involves some operations that is not feasible with a sequence, like indexed access operation which is only possible on a List (while you can still call

.toList()

on a sequence to do that, if this becomes a common use case, it might make more sense to just make it

List

)

Once 421 is merged, my understanding is that KSP could do a step forward towards KMP projects by starting to support multiple jvm targets in the same project, as in:

kotlin {
    jvm()
    jvm("foo")
}

Is this on the roadmap? One solution could be creating per-target ksp configurations like

kspJvmFoo

, inheriting from the root

ksp

. I'm happy to work on a PR if the team agrees with the plan.

brought this up a while ago but didn't seen any movement on it so decided to create a pr, let me know your thoughts! https://github.com/google/ksp/pull/422

Hi, here is the latest KSP release. Please note that we are pretty close to beta stage. In beta stage we want to avoid making API changes, if you have any changes you want to see in terms APIs, now is still a good time. This release is a pretty long one, please refer to the release note on Github for full list of changes in this release. Major breaking changes: • switch to 

Sequence

 for a bunch of APIs ◦ Some of the API return type has been changed from 

Collection

 or 

List

 to 

Sequence

, which will allow performance improvement if you use case involved early termination. ◦ Note that because 

Sequence

 is lazily evaluated, it requires a terminal operation to make actual compute happen. Please check you uses around the impacted APIs to see if they have a terminal operation. Most common use case is 

Collection.map{}

 which will iterate through the collection by itself, but is non-terminal for 

Sequence

 and should be companied with 

toList()

 or replaced with 

forEach

◦ For the whole list of APIs impacted by this change, please refer to this commit. • Origin for KS symbols from binaries is now split into 

KOTLIN_LIB

 and 

JAVA_LIB

.

Hi, we've moved the default branch of KSP from

master

to

main

. If you don't have a local copy of KSP source code, please feel free to ignore this message. If you do, you may want to update

origin

by

git branch -u origin/main <your-local-branch>

and

git remote set-head origin -a

.