Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
I do follow you a lot. Sometimes we exchanged some chat on Twitter too.
Few days ago you sent me a post in your blog about Colocation, which actually I had read already before you sent me that (we were chatting about streams for communicating through react components).
Sorry for the long preface, btw recalling that article, I would like to ask you one question about how do you structure usually jest configs instead.
It would be nice to know if you have any good practice about these setups and workflows, and if I missed the article I am sorry about it! (p.s. ofc I did read the one where you instead explain how do you place the related test files).
Just the little honor part, taken by what you all do for the community, I did write my first article on medium.
Thanks for the question @quirino-cargill!
I answered on my podcast: https://www.briefs.fm/3-minutes-with-kent/126
Congrats on the article :) That looks pretty idiomatic to me. Though I'm not sure I see the value in having
Which requires no abstraction. But yeah, great that you're encouraging people to use idiomatic React practices rather than making abstractions that make code less flexible and more confusing!
@kentcdodds Honored by your reply! will read carefully the link you shared if you covered these topics already!
Looks like I missed that article!
Yeah you got the point, there is not value in that component itself, it was just to show a simple example where to express that design pattern for designing components.
Thanks again for the time you spend for the community!
Have a good one!