Featured solution uses expect instead of allow as per what's suggested in the README

[boddhisattva]

Dear Project Collaborators,

I see that the featured solution is using expect instead of allow for the simple stub based on the code present here and here. The README of this project recommends using allow for stubs so would really appreciate if you could clarify on what's the correct thing to use for this exercise so that one could have a clear differentiation between when to use allow and when to use expect.

From what I've learnt in general, we use expect when we mutate data or for command methods in general and we use allow for query methods. It would be great if you could share your thoughts on what's more appropriate here and why you think that either of expect or allow is the more appropriate one in the context of this exercise, Thank you.

[yagosansz]

I think using expect feels weird because we have an expectation being defined in the setup phase of the test. I have used allow instead:

it "returns posts created today" do
  # setup
  posts = double("posts")
  dashboard = Dashboard.new(posts: posts)
  allow(posts).to receive(:today).and_return(posts)

 # exercise
  result = dashboard.todays_posts

  # verify
  expect(result).to eq(posts)
end

The only way to get dashboard.todays_posts to equal result is if #today is called on posts.