microstates / react Goto Github PK

I noticed this today while building a sample app with microstates. I have a TodoState type that looks like:

class TodoState {
  todos = [Todo];
  count = Number;

I think have a method that adds a todo to the list. In my methdo I am trying to

• add the todo to the list of todos
• increment the count

const inc = model => {
    model.count.increment();
    model.posts.push({ id: Date.now() });
  };

In the above code, the increment never happens, but the push WILL happen.

Here's a code sandbox of what I'm trying to do. If you flip lines 17 and 18, the increment will work.
https://codesandbox.io/s/13yv7ojlkl

I think we are at 0.10.x now.

It's the right thing to do.

I have a TodoState here, trying to initialize the todos prop like below.

export class TodoState {
  todos = [Todo];
  count = Number;

  initialize({ todos, count } = {}) {
    let initialized = this;
    initialized.todos.set([
      {
        id: Date.now(),
        text: "Initial Todo",
        complete: false
      }
    ]);
    initialized.count.set(1);
    return initialized;
  }
}
...
<State type={TodoState} ....></State>

I've even tried initialized.todos.push(...), but same Maximum call stack error. Am I doing something wrong here?

Before #1, the tests in this package ran against dist files. This is the same setup that we have in microstates repository. It allows us to catch any module export changes that could cause a problem in the package. For the sake of consistency, let's restore this functionality.

To make this work you have to run build before each test module by setting the globalSetup and moduleNameMapper.