Skip to content

Commit

Permalink
doc: remove stability highlight for stable functions
Browse files Browse the repository at this point in the history
We don't have the stability functions for all stable
functions, only those that were previously experimental and
then when stable. Remove the stability indicator to be
consistent with the rest of the functions.

PR-URL: #27753
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
  • Loading branch information
mhdawson authored and targos committed May 20, 2019
1 parent 026bebf commit f663e74
Showing 1 changed file with 0 additions and 22 deletions.
22 changes: 0 additions & 22 deletions doc/api/n-api.md
Original file line number Diff line number Diff line change
Expand Up @@ -284,16 +284,12 @@ This is an opaque pointer that is used to represent a JavaScript value.

### napi_threadsafe_function

> Stability: 2 - Stable

This is an opaque pointer that represents a JavaScript function which can be
called asynchronously from multiple threads via
`napi_call_threadsafe_function()`.

### napi_threadsafe_function_release_mode

> Stability: 2 - Stable

A value to be given to `napi_release_threadsafe_function()` to indicate whether
the thread-safe function is to be closed immediately (`napi_tsfn_abort`) or
merely released (`napi_tsfn_release`) and thus available for subsequent use via
Expand All @@ -307,8 +303,6 @@ typedef enum {

### napi_threadsafe_function_call_mode

> Stability: 2 - Stable

A value to be given to `napi_call_threadsafe_function()` to indicate whether
the call should block whenever the queue associated with the thread-safe
function is full.
Expand Down Expand Up @@ -402,8 +396,6 @@ typedef void (*napi_async_complete_callback)(napi_env env,

#### napi_threadsafe_function_call_js

> Stability: 2 - Stable

Function pointer used with asynchronous thread-safe function calls. The callback
will be called on the main thread. Its purpose is to use a data item arriving
via the queue from one of the secondary threads to construct the parameters
Expand Down Expand Up @@ -4600,8 +4592,6 @@ prevent the event loop from exiting. The APIs `napi_ref_threadsafe_function` and

### napi_create_threadsafe_function

> Stability: 2 - Stable

<!-- YAML
added: v10.6.0
napiVersion: 4
Expand Down Expand Up @@ -4644,8 +4634,6 @@ parameters and with `undefined` as its `this` value.

### napi_get_threadsafe_function_context

> Stability: 2 - Stable

<!-- YAML
added: v10.6.0
napiVersion: 4
Expand All @@ -4663,8 +4651,6 @@ This API may be called from any thread which makes use of `func`.

### napi_call_threadsafe_function

> Stability: 2 - Stable

<!-- YAML
added: v10.6.0
napiVersion: 4
Expand Down Expand Up @@ -4692,8 +4678,6 @@ This API may be called from any thread which makes use of `func`.

### napi_acquire_threadsafe_function

> Stability: 2 - Stable

<!-- YAML
added: v10.6.0
napiVersion: 4
Expand All @@ -4715,8 +4699,6 @@ This API may be called from any thread which will start making use of `func`.

### napi_release_threadsafe_function

> Stability: 2 - Stable

<!-- YAML
added: v10.6.0
napiVersion: 4
Expand Down Expand Up @@ -4744,8 +4726,6 @@ This API may be called from any thread which will stop making use of `func`.

### napi_ref_threadsafe_function

> Stability: 2 - Stable

<!-- YAML
added: v10.6.0
napiVersion: 4
Expand All @@ -4766,8 +4746,6 @@ This API may only be called from the main thread.

### napi_unref_threadsafe_function

> Stability: 2 - Stable

<!-- YAML
added: v10.6.0
napiVersion: 4
Expand Down

0 comments on commit f663e74

Please sign in to comment.