📚 Convention to differentiate between user and internal API #859
Labels
Status: Lack of interest
Issue went stale | cold | lack of (user) interest
Type: Documentation
Docs, Docs, Docs
Milestone
Version information
All
Describe the issue
If we have a way to differentiate between user API and internal API users shouldn't touch (use on own risk), we could quickly determine if we need proper deprecation to preserve the current behavior or if it is ok to change it.
Expected documentation
Something like
Internal API subject to changes, use on own risk!
or
We have some kind of allow list with all functions for the user API.
Additional context
For #851 we agreed that
Problem
isn't part of the official user API.The text was updated successfully, but these errors were encountered: