Skip to content

Move from KSP to classgraph for registration code and initial Scala support #761

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 32 commits into from
Apr 23, 2025

Conversation

piiertho
Copy link
Member

@piiertho piiertho commented Mar 4, 2025

This moves from KSP to classgraph to generate registration code.
This also adds initial Scala support to the module.

edit by @chippmann: resolves #773

@piiertho piiertho requested review from chippmann and CedNaru March 4, 2025 08:28
@piiertho piiertho self-assigned this Mar 4, 2025
@piiertho piiertho force-pushed the feature/classgraph-registration branch 2 times, most recently from 94d7905 to 249620c Compare March 5, 2025 06:52
@piiertho piiertho marked this pull request as ready for review March 5, 2025 08:55
Copy link
Contributor

@chippmann chippmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please also update the documentation accordingly.
Scala should at least be mentioned like java.
IMO we can add the scala specifics later in a separate PR but it is likely that this will be merged and released before that has happened. So I'd at least mention it.

Also: why not directly deleting the ksp implementation with this PR? currently there is no fallback where the user can fallback to the old symbol processor so i see no point in keeping that code around any longer.

@piiertho piiertho force-pushed the feature/classgraph-registration branch from 679e85f to e6456df Compare March 12, 2025 03:59
Copy link
Contributor

@chippmann chippmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very nice work!

I would not merge this in master though atm. This together with other big upcoming changes makes it harder to create bugfix releases in the meantime until these bigger tasks are finished.
Hence i propose to reintroduce a develop branch until these bigger changes are done.

@CedNaru CedNaru changed the base branch from master to develop April 22, 2025 15:57
Copy link
Member

@CedNaru CedNaru left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Took the liberty to create a develop branch and redirected the PR to it.
Otherwise, looks good to me for a first version. We'll see for more vicious potential bugs once we start using it for real.
I would also delete the ksp processor directory, but it can be done at a later point.

@piiertho piiertho force-pushed the feature/classgraph-registration branch from 5688880 to a5bbd42 Compare April 22, 2025 16:10
@piiertho piiertho merged commit 413eeb1 into develop Apr 23, 2025
64 checks passed
@piiertho piiertho deleted the feature/classgraph-registration branch April 23, 2025 15:09
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.

Type aliases aren't unwrapped when processing property, function, and signal registrations
3 participants