Nock
react-apollo
Nock | react-apollo | |
---|---|---|
21 | 8 | |
12,531 | 6,933 | |
0.3% | - | |
8.2 | 7.9 | |
5 days ago | almost 4 years ago | |
JavaScript | TypeScript | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Nock
-
Contract Testing?
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)
-
I made wirepig, a simple way to mock HTTP and TCP dependencies in tests.
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.
-
Is there a better way to mock an axios call?
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.
- How do you practice with React without setting up your own backend?
-
OSD600 - Telescope - Testing for feed URLs
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:
- What features would you consider missing/nice to haves for backend web development in Rust?
-
Axios shipped a buggy version and it broke many productions apps. Let this be a lesson to pin your dependencies!
There are libraries like https://github.com/nock/nock to prevent mocking the whole axios.
-
How to test an endpoint that depends on external API?
Use nock: https://github.com/nock/nock
-
How to mock a useQuery in jest?
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.
-
Is it acceptable to use mock servers, like Postman, for testing in Android?
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
react-apollo
-
Sending object's delta instead of whole object, for a subscription?
This apollo issue matches my problem: https://github.com/apollographql/react-apollo/issues/2866
-
5 tips for debugging Apollo GraphQL MockedProvider
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!
-
React-Apollo, don't run query on component load
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.
-
GraphQL with React Native
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?
-
GraphQL Code Generator - Introducing Hooks support for React Apollo plugin
React Apollo fits perfectly the requirements, and it now supports Hooks for your GraphQL operations.
-
Complex Apollo cache management with numerous parameterized queries made as painless as possible
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.
- Apolloclient Refetch All Instances Of This Query
What are some alternatives?
msw - Seamless REST/GraphQL API mocking library for browser and Node.js.
apollo-client - :rocket: A fully-featured, production ready caching GraphQL client for every UI framework and GraphQL server.
http-proxy - A full-featured http proxy for node.js
TanStack Query - 🤖 Powerful asynchronous state management, server-state utilities and data fetching for the web. TS/JS, React Query, Solid Query, Svelte Query and Vue Query.
node-fetch - A light-weight module that brings the Fetch API to Node.js
react-relay - Relay is a JavaScript framework for building data-driven React applications.
axios - Promise based HTTP client for the browser and node.js
adrenaline
superagent - Ajax for Node.js and browsers (JS HTTP client). Maintained for @forwardemail, @ladjs, @spamscanner, @breejs, @cabinjs, and @lassjs.
react-transmit
miragejs - A client-side server to build, test and share your JavaScript app
cerebral-module-http - HTTP module for Cerebral