Version 5.2.0-alpha.1

[coolsoftwaretyler]

Hey folks!

This is my first ever release as a MobX-State-Tree maintainer, so I'm planning on releasing alpha first, just to make sure things are looking good. Here's what changed!

Breaking changes

• No breaking changes

Features

• Add flag to determine if an action is a flow based action by @Slooowpoke in Add flag to determine if an action is a flow based action #1856
• give complex types debug names by @BrianHung in give complex types debug names #2049
• pass parent to default value function in t.optional by @BrianHung in pass parent to default value function in t.optional #2050

Fixes

• fix: throw error when creating a model with faulty name and valid pro… by @nithinssabu in fix: throw error when creating a model with faulty name and valid pro… #2048
• fix splitCache, extra nodes were being removed by @scytacki in fix splitCache, extra nodes were being removed #2054
• call lifecycle hooks after children are created by @scytacki in call lifecycle hooks after children are created #1952. Note: this should be only a fix, but it does technically alter some order-of-operations. We don't believe this to be a semantically breaking change, but we would love early feedback on the alpha build if folks have any problems with it.
• Add lazy type for lazy importing of models by @clgeoio in Add lazy type for lazy importing of models #1722
• Add two new primitives for MST by @chakrihacker in Add two new primitives for MST #2052

Docs

• docs: update references to example repos that will move external by @coolsoftwaretyler in docs: update references to example repos that will move external #2042
• chore: remove examples from repository by @coolsoftwaretyler in chore: remove examples from repository #2043
• docs: remove extra reference of packages/mst-example-bookshop by @JuanJo4 in docs: remove extra reference of packages/mst-example-bookshop #2047

Tests

• Test/add more test coverage for types model by @coolsoftwaretyler in Test/add more test coverage for types model #2044

Development/community only

• chore: update GitHub issue templates to focus on bugs by @coolsoftwaretyler in chore: update GitHub issue templates to focus on bugs #2017

New Contributors

• @coolsoftwaretyler made their first contribution in chore: update GitHub issue templates to focus on bugs #2017
• @Slooowpoke made their first contribution in Add flag to determine if an action is a flow based action #1856
• @JuanJo4 made their first contribution in docs: remove extra reference of packages/mst-example-bookshop #2047
• @nithinssabu made their first contribution in fix: throw error when creating a model with faulty name and valid pro… #2048
• @BrianHung made their first contribution in give complex types debug names #2049
• @scytacki made their first contribution in fix splitCache, extra nodes were being removed #2054
• @clgeoio made their first contribution in Add lazy type for lazy importing of models #1722
• @chakrihacker made their first contribution in Add two new primitives for MST #2052

Full Changelog: v5.1.8...v5.2.0-alpha.1

---

This discussion was created from the release Version 5.2.0-alpha.1.

[coolsoftwaretyler]

As a heads up for folks, we know that https://mobx-state-tree.js.org/ is in a funky state at the moment, where the API reference is ahead of the stable release.

There's a bit of a mismatch right now because we broke some links on the old docs site when we removed sample repos. We fixed that in this repo, which is tightly coupled to the auto-generated docs for the codebase. As we work to improve the documentation site, we should be able to fix that issue.

Sorry for the initial confusion! Once this release is out of alpha, the docs site will be correct with latest. Hoping to wait about a week on this release candidate, get feedback, and make it official.

[coolsoftwaretyler]

I'll be shipping this RC to my main production app in the coming week. We have a fairly large userbase, so I should be able to incrementally roll it out and get good samples on my end. I expect to tag this for full release sometime next week, assuming we don't run into any issues.

[coolsoftwaretyler]

We are going with the next candidate: #2076