Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[RFC] Experimental APIs
See original GitHub issueIn order to support API features that are likely to change (1.16 nether biome selection) or difficult to get right from the start, I am proposing to offer experimental APIs in Fabric API. Those APIs are marked via @Deprecated and can both extend existing modules or form new ones.
The @Deprecated annotation use is in line with how Java annotates its preview features, which serve a similar purpose. Additionally the associated Javadoc has to include @deprecated Experimental feature, may be removed or changed without further notice <optional explanation why it is experimental>.
Addition of and incompatible changes to experimental features will incur a minor version bump, the major version and module version (v0/v1/…) remain the same.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:22
- Comments:37 (29 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Quick vote: 👍 for guava
@Betaannotation etc. in addition to@Deprecatedon snapshot hooks 👎 for just@Deprecatedon snapshot hooksAnother quick note: We talked about jetbrain annotations has annotations like
@ApiStatus.Experimental, which may serve notification purposes with ide integration.