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.