Setup processing abstraction to lay the groundwork for KSP #152
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First step for #151
I've copied over the processing abstractions from https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:room/compiler-processing/ to allow the paris processor to share code between javac and KSP.
I've got the majority of the paris code converted to this abstraction, but some things like dealing with resources and packages are more difficult (and maybe impossible...) so KSP cannot be used quite yet.
All unit and instrumentation tests pass so this should be generally correct, but I will want to try it in our app with our screenshot testing to hopefully identify any small bugs. The code could also use a little clean up before merging still.