Hi there, we have made another <bi-weekly release>...
# ksp
t
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!
❤️ 3
🎉 9
z
Should
SymbolProcessorProvider
be a
fun interface
?
e
@Zac Sweers could be, I think. Although it (should) only be called by KSP, and maybe tests
z
Tests are what I’m thinking off. Definitely made things meatier when I updated some projects
e
I don't see any issues in making it a
fun interface
, so if you want to change it, feel free 🙂
t
Sounds good to me, too. If nobody is already working on this, I'll make a patch later.
👍 2
👍🏼 1
t
Nice as mentioned in the release notes and also by my tests i can tell that incremental processing now works for my project 👍
🎉 2