and apply it to existing inspections that rely on annotations on
property w/o use-sites (which technically don't belong to UField). #KTIJ-33663
GitOrigin-RevId: 2ff1de00976104ae33beed0b71e544354c7de606
Only `FIELD` or `PROPERTY_DELEGATE_FIELD` use-site targets are
applicable to fields. Also annotations whose meta-annotation targets
include `FIELD`, but not `PROPERTY`, e.g., @JvmField or
@ScheduledForRemoval
It is not trivial to figure out meta-annotation at UAST level (as it
will trigger expensive resolution). Instead, similar to KotlinUMethod
(where functions and property accessors need similar use-site
computation), we piggy-back on LC's use-site computation.
^KTIJ-33663 fixed
GitOrigin-RevId: 92b95b5ce6d27436d13d92bf40df40c861f884c6
Follow up to made comments in IJ-MR-156853 after it was already merged to master.
Merge-request: IJ-MR-157747
Merged-by: Bartek Pacia <bartek.pacia@jetbrains.com>
GitOrigin-RevId: 3b4ec6551c0d18f79eeff51954850327538fbeab
