为什么在这个 MobX 示例中需要 'get'

Question

在 MobX tutorial 的一部分中，一个示例使用 getter 语法来调用属性报告。

class ObservableTodoStore {
@observable todos = [];
@observable pendingRequests = 0;

constructor() {
    mobx.autorun(() => console.log(this.report));
}

@computed 
get completedTodosCount() {
    return this.todos.filter(
        todo => todo.completed === true
    ).length;
}

@computed 
get report() {
    if (this.todos.length === 0)
        return "<none>";
    return `Next todo: "${this.todos[0].task}". ` +
        `Progress: ${this.completedTodosCount}/${this.todos.length}`;
}

addTodo(task) {
    this.todos.push({
        task: task,
        completed: false,
        assignee: null
    });
}
}

const observableTodoStore = new ObservableTodoStore();

observableTodoStore.addTodo("read MobX tutorial");
observableTodoStore.addTodo("try MobX");
observableTodoStore.todos[0].completed = true;
observableTodoStore.todos[1].task = "try MobX in own project";
observableTodoStore.todos[0].task = "grok MobX tutorial";

// Next todo: "read MobX tutorial". Progress: 0/1
// Next todo: "read MobX tutorial". Progress: 0/2
// Next todo: "read MobX tutorial". Progress: 1/2
// Next todo: "grok MobX tutorial". Progress: 1/2

当我从报告中删除 get 关键字时属性,

@computed 
report() { 
// ...

然后更改对该报告的调用以反映它不再是 getter,

constructor() {
    mobx.autorun(() => console.log(this.report()));
}

然后我仍然得到控制台输出。然而，这是非常不同的。

// Next todo: "grok MobX tutorial". Progress: 1/7
// Next todo: "grok MobX tutorial". Progress: 1/8

为什么结果如此不同？我认为使用 getters 的决定更像是一种风格选择。

Answer 1

您需要将 get 与 @computed 装饰器结合使用。

computed decotator 的文档指出：

If you have decorators enabled you can use the @computed decorator on any getter of a class property to declaratively created computed properties.

为什么在这个 MobX 示例中需要 'get'

Why is 'get' necessary in this MobX example

javascript

mobx