If bound methods or fields are re-assigned, they become shared between instances

描述

class A {
  @boundMethod
  bound() {}
}

const a = new A();
const b = new A();
a.bound = {
  foo: 'bar'
};
assert.notEqual(a.bound, b.bound);

貢獻者指南

技術棧

javascript

領域

developer experiencetesting

議題類型

bug

難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。

3

預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。

half day

活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。

stale

清晰度議題是否清楚說明預期改動、驗收標準和下一步。

clear

前置要求

JavaScript class syntaxDecorator patternAutobinding

新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。

65

研究方向

The bug occurs when a bound method or field is reassigned on an instance, causing shared state across instances. To fix, examine the existing implementation of the boundMethod decorator (likely in src/index.js or similar). The test case provided in the issue description should be added to the test suite. A potential solution is to generate a new binding function or use a WeakMap to store original values per instance. See the issue comments for discussion on possible approaches, but no PRs are linked.