You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This CL fixes a bug KSP abstraction where it would consider any property
as a field even when the property does not have a backing field.
Now instead, we properly exclude them from fields list.
We also had another small bug where we didn't create fields for
companion properties. KAPT does so now we do as well. For that, I've
changed the KSDeclaration isStatic helper to check for companion
objects. It is necessary as `isStatic` is used for overrides, asMemberOf
etc. (asMemberOf won't work between a class and its companion).
We've hit a bug in KSP where backing field value is wrong for static
companion fields in the classpath so that test path is excluded for now:
google/ksp#491
Also fixed the declared fields implementation in KSP to properly return
based on backing field.
Bug: 177660733
Test: XTypeElementTest
Change-Id: I978c285e5b720bd8cbabb4df563a85153cbb5918
When a companion field is coming from a
.class
file,hasBackingField
always returns false.repro
yigit@c26fd51
The text was updated successfully, but these errors were encountered: