react-apollo VS Nock

This apollo issue matches my problem: https://github.com/apollographql/react-apollo/issues/2866

We’re heavy users of Apollo GraphQL in my team at Swarmia, but sometimes mocking the queries is bothersome. And based on a few GitHub comments, it looks like we’re not alone. This blog post is here to help!

I'm using the awesome https://github.com/apollographql/react-apollo library and I'm trying to see if there is a better convention to load data into components than how I'm doing it now.

Hello guys, I'm working with GraphQL using Apollo Client and facing a big issue but haven't found a fix yet. The problem is with fetchMore callback. This trigger twice, one is the original call, second is the call with new variables. But onComplete only return the response of the original one. When I use nextFetchPolicy: "cache-first" it not trigger the original variables anymore, but the onComplete doesn't return the result of new call. I've looking for a solution on the internet and found this: https://github.com/apollographql/react-apollo/issues/2177 But a few years passed and there aren't any explain or fix. It makes me nervous about choosing apollo client for long-term usage. Can you suggest a client that still has maintainers?

React Apollo fits perfectly the requirements, and it now supports Hooks for your GraphQL operations.

I've been using Apollo for a couple of years now, and it is infamously nebulous when it comes to moderately complex real-world scenarios, such as parameterized queries. There are many years-spanning github issues on this problem alone, with barely any maintainable solutions proffered. I've written a lengthy guide that explains exactly how Apollo's InMemoryCache works under the hood and how to sanely solve these caching issues.

So, why would you want a REAL server to mock request/reponses? You have a lot of intercepts today that sit on the network layer and you can define things like "If you send request to that endpoint, with that json, please return that Status" (for NodeJS example, Nock - https://github.com/nock/nock)

That said, folks seem to like "recording" features in these sorts of tools (Ruby's VCR, nock, etc), so maybe there's a future where I add something similar. I've always just found the ergonomics of those features awkward to deal with, especially having to flip back and forth between tests and fixtures files to figure out what's wired to what, but maybe there's a clean solution... perhaps a "live request" mode that just prints mock code snippets of request/response pairs passing through your app.

While not mocking per say I usually use nock for http calls. You can use nock.recorder.rec() to capture the http call to play back during test, That way you are always using "live" code but not making real calls to servers.

I looked at the service which is used to get the feed URLs from a blog URL and noticed it takes the html response of the blog URL and gets the links ( tags) by checking the type attribute value against a list of valid feed values. So, I decided to use a similar approach by getting the html response for a provided URL and checking the Content-Type header against a list of valid MIME types for a feed. I ended up updating the logic to test if a URL is a feed URL, returning it if true. If the URL is found to not be a feed URL, it would try to get the feed URLs assuming the URL is a blog URL. I tested and confirmed that the new logic worked for both blog and feed URLs. Then, I added some tests for the new function I added to test for a feed URL. Testing this ended up being simpler than I expected as all I had to do was mock the response of a test url (using nock), and then check if the function returned the correct boolean value for a url. I created a PR and noticed that some of the tests in another file were now failing. While I was investigating this, I got a review on my PR, requesting me to add another test to the file which had the failing tests. That file tested the API service as a whole. I found out that nock only mocks a URL's response for one request by default. And since I was now checking for a feed URL as well, the function which returned the feed URLs from a blog URL was throwing an error since the nock for that was used up. To fix this, I had to specify in the nock statement to mock the URL response for two requests:

There are libraries like https://github.com/nock/nock to prevent mocking the whole axios.

Use nock: https://github.com/nock/nock

Going based off the documentation I sent you in my last reply, there is an example that uses nock to emulate api responses. I haven't used nock myself, but the example seems pretty simple to use. You just need to take the example and change the response object to be the shape of what your getStuffFromDatabase function returns. That way your useCategory function runs as close to normally as possible, while providing a mock response value instead of hitting the database.

If you’re willing to venture into nodejs territory, then nock is a fantastic and simple to set up http mock server. https://github.com/nock/nock