You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 1-js/99-js-misc/01-proxy/article.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -840,7 +840,7 @@ So there's no such problem when proxying an array.
840
840
841
841
### Private fields
842
842
843
-
The similar thing happens with private class fields.
843
+
A similar thing happens with private class fields.
844
844
845
845
For example, `getName()` method accesses the private `#name` property and breaks after proxying:
846
846
@@ -963,7 +963,7 @@ revoke();
963
963
alert(proxy.data); // Error
964
964
```
965
965
966
-
A call to `revoke()` removes all internal references to the target object from the proxy, so they are no more connected. The target object can be garbage-collected after that.
966
+
A call to `revoke()` removes all internal references to the target object from the proxy, so they are no longer connected. The target object can be garbage-collected after that.
967
967
968
968
We can also store `revoke` in a `WeakMap`, to be able to easily find it by a proxy object:
0 commit comments