-
Notifications
You must be signed in to change notification settings - Fork 160
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
Use explicit API mode #535
Comments
Great. I have a branch forked from my k2 brach that adds the binary compatibility validation. On holiday this week but I can add this to it when back. Will pr that branch once k2 is merged, but since I also added ktlint it's rather big so keeping it separate for readability |
That would be great! I would like to finish this PR and other breaking changes such as removing the exposed internal functions and roll it all into a single major version release, 2.0.0 (which also syncs nicely with upgrading to Kotlin 2.0) |
With explicit API mode, you must:
Add visibility modifiers to your declarations to make them public, instead of relying on the default public visibility. This ensures that you've considered what you're exposing as part of the public API.
Define the types for all your public functions and properties to prevent unintended changes to your API from inferred types.
https://kotlinlang.org/docs/whatsnew14.html#explicit-api-mode-for-library-authors
The text was updated successfully, but these errors were encountered: