Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OverrideOnly API declared within plugin and invoked from the plugin itself should not be reported #1103

Merged
merged 6 commits into from
Jul 3, 2024

Conversation

novotnyr
Copy link
Collaborator

@novotnyr novotnyr commented Jun 27, 2024

If the plugin defines an API with @ApiStatus.OverrideOnly, the invocations of such API elements from the plugin itself should not be reported as problems.

  • Declare an ApiUsageFilter that allows same-module invocations

@YannCebron
Copy link
Member

YannCebron commented Jun 27, 2024

It must take into account all ApiStatus variants. https://youtrack.jetbrains.com/issue/MP-6680 could we please have some tests for the others as well?

@novotnyr
Copy link
Collaborator Author

It must take into account all ApiStatus variants. https://youtrack.jetbrains.com/issue/MP-6680 could we please have some tests for the others as well?

Other annotations have a different mechanisms. I suggest focusing this PR on the OverrideOnly. Other ApiStatus-es will be targeted by the subsequent PR.

@novotnyr novotnyr merged commit 0e6978b into master Jul 3, 2024
2 checks passed
@novotnyr novotnyr deleted the overrideonly-in-same-jar branch July 3, 2024 21:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants