Introduce Kotlin Explicit API mode to core-xxx modules
See original GitHub issueIdea Description
Explicit visibility using public
or internal
or private
allows you to control what expose outside the module. Kotlin default visibility is public
, so you may expose things you don’t want to be public.
You can force explicit visibility using Kotlin Explicit API mode. It helps control visibility.
⚠️ Applying Explicit API mode requires changing many parts of existing code.
Issue Analytics
- State:
- Created a year ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Android Developer Fundamentals Course – Concepts
Java API Framework: All features of Android are available to developers through ... Activity launch modes, to determine how an activity should be...
Read more >Kotlin Cookbook - NIBM eHub
manual provides a solid introduction to the language, ... it from Java without having to specify explicit values for each parameter.
Read more >javajni - OSCHINA - 中文开源技术交流社区
为了使用底层的主机平台的某个特性,而这个特性不能通过JAVA API拜访 2. ... Invocation API(JNI 的一部分)可以用来将Java 虚拟机(JVM)嵌入到本机应用程序中,从而 ...
Read more >The Most Trusted Dating Site
Find a one-night stand or a hookup you can also hang out with. Which dating site is best for serious relationships? What is...
Read more >Untitled
Find a one-night stand or a hookup you can also hang out with. Which dating site is best for serious relationships? What is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you for your decision🙇 I’d like to make a PR to add “
explicitApiWarning()
” to core-xxx module’s “build.gradle.ktx” soon.@d1-morimoto Sorry for keeping you waiting 🙇 Let’s use explicitApiWarning! The reason is if you create the plugin or extension for it, it will probably provide the same API, and there are no pros.