Me again :)
What is the purpose of removing the stubbing and adding rewire$fetch?
There is now no way to mock the return value of fetch which I thought was the point.
I think I may be a bit lost.
I'm wondering if it's because you split the testing of the store out to it's own spec and you test the fetch in there. Then you don't need to retest that in the Component spec.. Is that correct?
Correct :)
š¤£
I think I confused this by aliasing fetch as fetchPrice, but leaving rewire$fetch instead of naming that rewire$fetchPrice.
fetch
fetchPrice
rewire$fetch
rewire$fetchPrice
Thanks for this feedback. I need to work on this a little!
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Me again :)
What is the purpose of removing the stubbing and adding rewire$fetch?
There is now no way to mock the return value of fetch which I thought was the point.
I think I may be a bit lost.
I'm wondering if it's because you split the testing of the store out to it's own spec and you test the fetch in there. Then you don't need to retest that in the Component spec.. Is that correct?
Correct :)
š¤£
I think I confused this by aliasing
fetch
asfetchPrice
, but leavingrewire$fetch
instead of naming thatrewire$fetchPrice
.Thanks for this feedback. I need to work on this a little!