Skip to content

Conversation

idanakav
Copy link

Resolves #1035

Sanity tested with:

cd examples/ksp ; bazel aquery 'mnemonic(KotlinKsp, //:coffee_lib)' | grep ksp_opts -A 2

    --ksp_opts \
    'arg1=value1' \
    'arg2=value2' \

This commit adds the support to pass options to KSP processors, currently it the support is added on a target level only.
Eventually the options are passed through the kotlinc:
`-P google.devtools.ksp.symbol-processing:apoption=key=value`
@restingbull
Copy link
Collaborator

Does KSP fail if flags for absent plugins are passed?

@idanakav
Copy link
Author

Does KSP fail if flags for absent plugins are passed?

No, those are generic KSP options that are going to be forwarded to any KSP processor.
In other words, any KSP processor listed in the plugins will receive the same options.

@restingbull
Copy link
Collaborator

Does KSP fail if flags for absent plugins are passed?

No, those are generic KSP options that are going to be forwarded to any KSP processor. In other words, any KSP processor listed in the plugins will receive the same options.

Shoot. Going to need to track the plugin that needs the arguments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Missing support for passing options to KSP processors
2 participants