Refactoring for the Better or Worse?
Let's perform a round of refactoring in this episode. But there's a twist! At the conclusion of the refactor, we'll take a very important step. That step is to ask ourselves, "Is the code better as a…
Let's perform a round of refactoring in this episode. But there's a twist! At the conclusion of the refactor, we'll take a very important step. That step is to ask ourselves, "Is the code better as a…
We can finally switch over to the client-side, and begin constructing a user-notifications Vue component that will be responsible for fetching all relevant notifications and rendering them within a…
Let's take a few moments to refactor the tests in our NotificationsTest class. A handful of tweaks should make this file far more simple to read and understand six months from now.
Now that a thread exposes the behavior that it can be subscribed to, we can move on to preparing all relevant user notifications each time the thread receives a new reply. To allow for this, we'll le…
I was recently listening to an episode of Twenty Percent Time, where they discussed one of the recommendations in my Whip Monstrous Code into Shape series that relates to using single-use traits. In…
Let's take a bit of time to work on the UI side of things. We need to prepare a "Subscribe" Vue component that handles the behavior of toggling the current user's subscription to any given thread. Vi…