Graphql 调用 Axios 多次调用性能/重构

Question

I'm able to delete and add data into my JSON file, but if I keep pressing the button (toggling add/delete), I get a network failure. I'm assuming that I can't make multiple requests like this?

const handleSave = save => {
  if (save.toLowerCase() === 'save') {
    props
      .addSaved({
        variables: {
          id: props.id,
        },
      })
      .then(res => {
        setSaved('Unsave');
        setSavedPropData(res.data.addSaved);
      });
  } else {
    props
      .deleteSaved({
        variables: {
          id: savedPropData.id,
        },
      })
      .then(() => setSaved('Save'));
  }
};

The above is the snippet of my handle saving data. So each press it toggle's Save or Unsave, and then it will add or delete data into my JSON. I'm currently using json server to test the application.

const savedMutate = gql`
  mutation addSaved($id: String) {
    addSaved(id: $id) {
      id
    }
  }
`;

const deletedMutate = gql`
  mutation deleteSaved($id: String) {
    deleteSaved(id: $id) {
      id
    }
  }
`;

export default _.flowRight(
  graphql(savedMutate, {name: 'addSaved'}),
  graphql(deletedMutate, {name: 'deleteSaved'}),
)(withNavigation(Card));

Is there a better way to doing this if I deploy the application into production? Currently I get the network failure when I'm toggling fast. I just tried again, is it because my app refreshes every time and while its refreshing, I'm trying to save into my database, but it hasn't been fully mounted? Is this only happening in development?

mutation:

addSaved: {
  type: SavedType,
  args: {
    id: {type: GraphQLString},
  },
  resolve(parentValue, {id}) {
    return axios
      .post(`http://localhost:3000/saved`, {id})
      .then(res => res.data);
  },
},
deleteSaved: {
  type: SavedType,
  args: {
    id: {type: GraphQLString}
  },
  resolve(parentValue, {id}) {
    return axios
      .delete(`http://localhost:3000/saved/${id}`)
      .then(res => res.data);
  },
},

Answer 1

If you're running your server with nodemon and you're writing to some file in response to requests and this file is being watched by nodemon, then your requests will always trigger a server restart. Since the first request restarts the server, any requests that follow immediately after will fail because your server will now be down while it is starting back up.

You need to configure nodemon to ignore the appropriate files or directories . This way, any changes to the files won't cause nodemon to restart your server.