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
Without this, file annotations are not considered when filtering the classes with non-public markers. Please find the reproducer in the attached pull request.
The text was updated successfully, but these errors were encountered:
dovchinnikov
added a commit
to dovchinnikov/binary-compatibility-validator
that referenced
this issue
Jan 8, 2024
File-targeting annotations (@file:..) seem to be only emitted for file-facade classes, and in all other cases, they are just lost.
If a file contains top-level declarations and has some @file-annotation registered as a non-public marker, a facade class generated to hold these declarations will be filtered out from the dump.
I mean, there's no info about such an annotation (except the file-facade case), so there's nothing we can do on the BCV side at the moment.
Trying to figure out how @file-annotations are supposed to work (and if they are supposed to work the way they do).
Without this, file annotations are not considered when filtering the classes with non-public markers. Please find the reproducer in the attached pull request.
The text was updated successfully, but these errors were encountered: