From 10c8197478284c9109a93fd2380b2618c4e2acee Mon Sep 17 00:00:00 2001 From: godzylinux Date: Tue, 7 May 2024 21:10:14 +0330 Subject: [PATCH] better describe what `mutation_properties` does --- packages/svelte/src/reactivity/utils.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/svelte/src/reactivity/utils.js b/packages/svelte/src/reactivity/utils.js index d7b02e38c1..5484f509e2 100644 --- a/packages/svelte/src/reactivity/utils.js +++ b/packages/svelte/src/reactivity/utils.js @@ -41,7 +41,7 @@ function get_this() { * @template TEntityInstance * @template {(keyof TEntityInstance)[]} TMutationProperties * @typedef {object} Options - * @prop {TMutationProperties} mutation_properties - an array of property names on `TEntityInstance`. when calling a property on `TEntityInstance`, if the property name exists in this array, then mentioned property is made reactive. + * @prop {TMutationProperties} mutation_properties - an array of property names on `TEntityInstance`. when calling a property on `TEntityInstance`, if the property name exists in this array, then mentioned property causes reactivity. * @prop {Interceptors} [interceptors={}] - if the property names in `mutation_properties` shouldn't be always reactive, such calling `set.add(2)` twice, you can prevent the reactivity by returning false from these interceptors */