It's fair to assume that we have some reference to an object that performs the network fetch and we know when it completes its job.
In this case, we can just execute the same fetch request again and be done. There'll be cases when a user's profile updates because of other network operations in our app.
If that happens we'll end up with a stale data visible on the screen.
The recommended approach to working around that in Core Data are notifications. We have to handle initial fetch and future updates in (two) completely different ways. It's not just me too, as it's against current development practices, such as FRP.
Some plugins and CSS components depend on other plugins.
If you include plugins individually, make sure to check for these dependencies in the docs.
This is the second article for our Core Data series.