-
I think a test case that reproduces this problem explains it best:
```ts
import {
getSnapshot,
Model,
model,
modelAction,
prop,
registerRootStore,
} from 'mobx-keystone';
tes…
-
### Issue description or question
PLEASE NOTE: If you are using If you are using Jest >= v24 or Angular CLI >= v8.2 and using a
wallaby configuration file, switching to use automatic configuration…
-
I've noticed inconsistent results of an action (move element to the end of an array) vs. `applyPatches` vs. `applySnapshot` when using a (root) ref which removes the node when it cannot be resolved an…
-
Hi, thanks for the awesome work on mobx-keystone
I am really excited to move from MST for TS compatibility reasons
However, I've ran into an issue with decorators and class fields
The condensed e…
-
After upgrading to v0.17, I'm getting the following error:
```
mobx-keystone.esm.js:110 Uncaught Error: assertion failed: value is not ready to take a parent
at failure (mobx-keystone.esm.js:…
-
> References in mobx-state-tree were designed to be transparent to the user. Maybe way too transparent, up to a level where there’s no way, for example, to get the parent of a reference node. In mobx-…
-
There seems to be a problem with `getRefsResolvingTo` after loading the state from a snapshot. Specifically, I'm retrieving backreferences in a computed property which uses `getRefsResolvingTo` and al…
-
When using `ExtendedModel` in a `create-react-app`-based app, I'm getting the following error:
> TypeError: Class constructor [...] cannot be invoked without 'new'
This is a minimal reproduction…
-
Imagine the following case:
```ts
@model("myApp/A")
class A extends Model({
b: prop()
}) {}
@model("myApp/B")
class B extends Model({}) {}
```
`A.b` is a reference of `B`, but `B` doe…
-
Since #50 and #51, does it make sense to let `BaseModel::getRefId` return `this.$modelId` by default?