Weekly Digest (11 November, 2018 - 18 November, 2018)

[weekly-digest]

Here's the Weekly Digest for microstates/microstates.js:

---

ISSUES

Last week 7 issues were created.
Of these, 3 issues have been closed and 4 issues are still open.

OPEN ISSUES

💚 #278 Codesandboxes for documentation examples , by eandy5000
💚 #277 Failing test for transitioning microstates with initial value, by minkimcello
💚 #276 Added object iterator to allow using ObjectType with queries, by taras
💚 #273 How to get Type of a microstate?, by taras

CLOSED ISSUES

❤️ #279 No special case for the set transition., by cowboyd
❤️ #275 Added remove transition to ArrayType, by taras
❤️ #274 Should ArrayType type have a remove transition?, by taras

LIKED ISSUE

👍 #274 Should ArrayType type have a remove transition?, by taras
It received 👍 x2, 😄 x0, 🎉 x0 and ❤️ x0.

NOISY ISSUE

🔈 #276 Added object iterator to allow using ObjectType with queries, by taras
It received 8 comments.

---

PULL REQUESTS

Last week, 4 pull requests were created, updated or merged.

UPDATED PULL REQUEST

Last week, 2 pull requests were updated.
💛 #277 Failing test for transitioning microstates with initial value, by minkimcello
💛 #276 Added object iterator to allow using ObjectType with queries, by taras

MERGED PULL REQUEST

Last week, 2 pull requests were merged.
💜 #279 No special case for the set transition., by cowboyd
💜 #275 Added remove transition to ArrayType, by taras

---

COMMITS

Last week there were 3 commits.
🛠️ Merge pull request #279 from microstates/cl/set-as-transition No special case for the set transition. by cowboyd
🛠️ No special case for the set transition. Microstate transitions are like a transaction. You start with a microstate, and what is returned is the next wersion of that microstate. However, this transaction was being spread over two methods: the actual transition invocation and the set method. In other words, the transition method was just called, and then the "work" was happening in set. As we move the codebase to have more interesting outcomes inside a single transition like being able to transition to different parts of the store, we'll need to be able to reason about what exactly a state transition is in a single place. This change places all of the transition logic in a single location: the transition method, and set becomes just another transition that isn't at all special except for the fact that a default implemenation (the identity function) is provided for it without you having to specify it in the class definition. Having no special transitions will give us the power to make changes to transition semantics without having to worry about corner cases. by cowboyd
🛠️ Added remove transition (#275) by taras

---

CONTRIBUTORS

Last week there were 2 contributors.
👤 cowboyd
👤 taras

---

STARGAZERS

Last week there were 24 stagazers.
⭐ taras
⭐ arusanov
⭐ AzSiAz
⭐ raypatterson
⭐ s-oram
⭐ 77ukhtar
⭐ jam-lw
⭐ hieuvoquang87
⭐ behzad888
⭐ pankaz
⭐ KhaledElAnsari
⭐ davidosomething
⭐ AndroConsis
⭐ joetheace107
⭐ EmreErdogan
⭐ XaveScor
⭐ mkoczka
⭐ vunguyenhung
⭐ awinogradov
⭐ sburnicki
⭐ gangsthub
⭐ devsnice
⭐ qdouble
⭐ katallaxie
You all are the stars! 🌟

---

RELEASES

Last week there were no releases.

---

That's all for last week, please 👀 Watch and ⭐ Star the repository microstates/microstates.js to receive next weekly updates. 😃

You can also view all Weekly Digests by clicking here.

Your Weekly Digest bot. 📆