Skip to content

Commit f663e74

Browse files
mhdawsontargos
authored andcommitted
doc: remove stability highlight for stable functions
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 <[email protected]> Reviewed-By: Sam Roberts <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: James M Snell <[email protected]>
1 parent 026bebf commit f663e74

File tree

1 file changed

+0
-22
lines changed

1 file changed

+0
-22
lines changed

doc/api/n-api.md

-22
Original file line numberDiff line numberDiff line change
@@ -284,16 +284,12 @@ This is an opaque pointer that is used to represent a JavaScript value.
284284

285285
### napi_threadsafe_function
286286

287-
> Stability: 2 - Stable
288-
289287
This is an opaque pointer that represents a JavaScript function which can be
290288
called asynchronously from multiple threads via
291289
`napi_call_threadsafe_function()`.
292290

293291
### napi_threadsafe_function_release_mode
294292

295-
> Stability: 2 - Stable
296-
297293
A value to be given to `napi_release_threadsafe_function()` to indicate whether
298294
the thread-safe function is to be closed immediately (`napi_tsfn_abort`) or
299295
merely released (`napi_tsfn_release`) and thus available for subsequent use via
@@ -307,8 +303,6 @@ typedef enum {
307303

308304
### napi_threadsafe_function_call_mode
309305

310-
> Stability: 2 - Stable
311-
312306
A value to be given to `napi_call_threadsafe_function()` to indicate whether
313307
the call should block whenever the queue associated with the thread-safe
314308
function is full.
@@ -402,8 +396,6 @@ typedef void (*napi_async_complete_callback)(napi_env env,
402396

403397
#### napi_threadsafe_function_call_js
404398

405-
> Stability: 2 - Stable
406-
407399
Function pointer used with asynchronous thread-safe function calls. The callback
408400
will be called on the main thread. Its purpose is to use a data item arriving
409401
via the queue from one of the secondary threads to construct the parameters
@@ -4600,8 +4592,6 @@ prevent the event loop from exiting. The APIs `napi_ref_threadsafe_function` and
46004592

46014593
### napi_create_threadsafe_function
46024594

4603-
> Stability: 2 - Stable
4604-
46054595
<!-- YAML
46064596
added: v10.6.0
46074597
napiVersion: 4
@@ -4644,8 +4634,6 @@ parameters and with `undefined` as its `this` value.
46444634

46454635
### napi_get_threadsafe_function_context
46464636

4647-
> Stability: 2 - Stable
4648-
46494637
<!-- YAML
46504638
added: v10.6.0
46514639
napiVersion: 4
@@ -4663,8 +4651,6 @@ This API may be called from any thread which makes use of `func`.
46634651

46644652
### napi_call_threadsafe_function
46654653

4666-
> Stability: 2 - Stable
4667-
46684654
<!-- YAML
46694655
added: v10.6.0
46704656
napiVersion: 4
@@ -4692,8 +4678,6 @@ This API may be called from any thread which makes use of `func`.
46924678

46934679
### napi_acquire_threadsafe_function
46944680

4695-
> Stability: 2 - Stable
4696-
46974681
<!-- YAML
46984682
added: v10.6.0
46994683
napiVersion: 4
@@ -4715,8 +4699,6 @@ This API may be called from any thread which will start making use of `func`.
47154699

47164700
### napi_release_threadsafe_function
47174701

4718-
> Stability: 2 - Stable
4719-
47204702
<!-- YAML
47214703
added: v10.6.0
47224704
napiVersion: 4
@@ -4744,8 +4726,6 @@ This API may be called from any thread which will stop making use of `func`.
47444726

47454727
### napi_ref_threadsafe_function
47464728

4747-
> Stability: 2 - Stable
4748-
47494729
<!-- YAML
47504730
added: v10.6.0
47514731
napiVersion: 4
@@ -4766,8 +4746,6 @@ This API may only be called from the main thread.
47664746

47674747
### napi_unref_threadsafe_function
47684748

4769-
> Stability: 2 - Stable
4770-
47714749
<!-- YAML
47724750
added: v10.6.0
47734751
napiVersion: 4

0 commit comments

Comments
 (0)