@BenLesh While it help to separate state then side effects, you can still inadvertently renter. Often run into this subtle gotcha in redux observables https://t.co/pyPoCI6ZR1
@samselikoff Yes, changing it to a const fixes this. It’s more confusing when accessing the outer functions parameter values as parameters are let/mutable by default (but subtlety so), and would therefore unfortunately require you to reassign to a const.
@andybudd Reminds me of this quote from Jobs “You know who the best managers are? They’re the great individual contributors, who never ever want to be a manager, but decide they have to be a manager because no one else is going to be able to do as good a job as them.”
@acemarke Ah yes I think wrap slice would be what I was looking for originally. However there are some pros/cons to adding to an action to weigh up. (Should be able to add sterilisable “context” as opposed to the logger instance it’s self). Thanks 🙏
@acemarke … I created a middleware to add a logger to the action meta which seems to fit with the state/action pattern. Before RTK we used to “create” a reducer with a logger in the closure, but this isn’t possible with the config approach of creating a slice in toolkit.
@acemarke In this use case it’s a runtime logger (which uploads to server, adds context etc). It’s technically a side effect, but not in terms of affecting state (exceptions aside I guess).
Most business books be like...
Chapter 1. The authors life story
Chapter 2. The actual idea (which could have been a blog post)
Chapters 3-12. Carefully chosen anecdata to prove the idea
As a short cut, you can usually just read chapter 2 and skip the rest.
@acdlite It’s been over a year and I’m still woefully inconsistent, I’m not convinced the people on YouTube are actually using milk… https://t.co/aUPdh7FjuU