Skip to content

Missing support for passing options to KSP processors #1035

Open
@idanakav

Description

@idanakav

KSP offers a way to pass options to processors, its done with the -P flag, for example:

-P plugin:com.google.devtools.ksp.symbol-processing:apoption=key=value

Since we don't have a dedicated attr for that and the existing kotlinc opts are not supporting -P it's impossible to pass those options to the KSP plugin.

We probably would want to allow declaring the options on both target and processor level.

Activity

linked a pull request that will close this issue on Sep 29, 2023
restingbull

restingbull commented on Sep 29, 2023

@restingbull
Collaborator

Does KSP fall on unknown options?

idanakav

idanakav commented on Oct 3, 2023

@idanakav
Author

Does KSP fall on unknown options?

In general , yes, since kotlinc will throw on unknown options, but in the case of apoptions it simply going to split by = and pass down the key values.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      Participants

      @idanakav@restingbull

      Issue actions

        Missing support for passing options to KSP processors · Issue #1035 · bazelbuild/rules_kotlin