-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Audit Experimental APIs #17743
Comments
There was this idea to build a tool which list all the experimental APIs: #15754. |
|
|
There are some packages that we should probably clean up right way, see:
The number of changes required shouldn't be that big there and those are lower-level packages so it should be easier to make a decision. Having a tool would help moving forward, we could reason what has changed between major releases. In addition, it would be easier to keep track of new unstable/experimental APIs introduced. There is #15754 proposed by @nosolosw which would work for everything that is exposed with the |
@aduth @nerrad @jorgefilipecosta @ellatrix @noisysocks @gziolo and others, if you worked on APIs that you think are worth considering stable, please consider opening a PR to propose it. |
Sure thing. In addition to that, I can explore what we can do about:
I know that the mobile team introduced |
Could we put all of the experimental / unstable APIs into a spreadsheet and collaborate on deciding which ones we want to promote? |
I don't have any other additions on that list. |
It's part of the block definition so it should be included in JSDoc comments and developer docs. Ideally, it should be covered in the tutorials as well. |
I did a quick check on that PR and saw that actually there's a different case there, dropped a comment. I've opened a new issue to track the effort for making |
There is a new issue to track the experimental API's in 5.4 #20116, I guess we can close this one. |
Over time and to avoid the locks of backward compatibility, we added a number of experimental APIs. We should take some time to audit all of these, remove or mark unstable the ones that we think are not going to be public APIs, and potentially stabilize the ones that we're confident about.
The text was updated successfully, but these errors were encountered: