Giter Club home page Giter Club logo

node-apollo-boost-github-graphql-api's Introduction

The Road to GraphQL [Book]

Slack

Official repository for The Road to GraphQL. If you want to leave a review, please do it on Amazon or Goodreads.

Translations of the book into Github

The Road to GraphQL is also available in other languages. Thanks for all translators for their awesome work!

Updates, Help and Support

Contribute

You can help to improve the book by opening Issues and Pull Requests (PR).

You can open up any PR that corrects spelling or explains a certain lesson with more detail. When writing such a technical book, you get fast blind on what needs more explanation and on what is already explained well.

In addition, you can open Issues when you run into problems. In order to make the fix for the Issue as easy as possible, please provide a couple of details such as error log, screenshot, which page of the book it happened, your node version (command line: node -v) and a link to your own repository. Not all of these details are mandatory, but most of them help to fix the Issue and to improve the book.

Thanks a lot for your help!

node-apollo-boost-github-graphql-api's People

Contributors

greenkeeper[bot] avatar rwieruch avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

node-apollo-boost-github-graphql-api's Issues

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Typo

Hi.

Maybe a small typo....

In the block with // resolve first page you write:
console.log('second page', edges.length)

It should be 'first page' right? :) .

Henrik

orderBy not working as expected

First of all, thanks to @rwieruch for the course!

I'm trying out the exercises at the end of the Apollo Client with Pagination, Variables, Nested
Objects and List Fields
chapter, and have encountered a problem querying the GitHub API where the orderBy argument appears to be ignored.

Query:

query ($organization: String!) {
  organization(login: $organization) {
    name
    url
    repositories(first: 5, orderBy: {field: STARGAZERS, direction: DESC}) {
      edges {
        node {
          name
          url
          stargazers {
            totalCount
          }
        }
      }
    }
  }
}

Variables:

{
  "organization": "the-road-to-learn-react"
}

Response:

{
  "data": {
    "organization": {
      "name": "The Road to learn React",
      "url": "https://github.com/the-road-to-learn-react",
      "repositories": {
        "edges": [
          {
            "node": {
              "name": "react-lift-state",
              "url": "https://github.com/the-road-to-learn-react/react-lift-state",
              "stargazers": {
                "totalCount": 0
              }
            }
          },
          {
            "node": {
              "name": "use-with-viewbox",
              "url": "https://github.com/the-road-to-learn-react/use-with-viewbox",
              "stargazers": {
                "totalCount": 1
              }
            }
          },
          {
            "node": {
              "name": "the-road-to-learn-react-albanian",
              "url": "https://github.com/the-road-to-learn-react/the-road-to-learn-react-albanian",
              "stargazers": {
                "totalCount": 1
              }
            }
          },
          {
            "node": {
              "name": "react-router-nested-routes-example",
              "url": "https://github.com/the-road-to-learn-react/react-router-nested-routes-example",
              "stargazers": {
                "totalCount": 2
              }
            }
          },
          {
            "node": {
              "name": "react-usereducer-hook",
              "url": "https://github.com/the-road-to-learn-react/react-usereducer-hook",
              "stargazers": {
                "totalCount": 3
              }
            }
          }
        ]
      }
    }
  }
}

The results are always returned in ascending order no matter what direction is passed in. I have also tried cloning this repo, and adding in some additional console.log output I can see that the same thing happens.

I have tried checking the documentation in graphiql and the query appears to be correct so it may actually be an issue with the API itself, just thought I would point it out in case anyone else encounters this same issue and finds it confusing!

An in-range update of nodemon is breaking the build 🚨

The devDependency nodemon was updated from 1.18.5 to 1.18.6.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

nodemon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for v1.18.6

1.18.6 (2018-11-05)

Bug Fixes

Commits

The new version differs by 1 commits.

  • 521eb1e fix: restart on change for non-default signals (#1409) (#1430)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Pagination Issue

I tried to apply pagination.

First of all, I fetched my first 10 repositories. Then I fetch another 10. Till this point, everything is okay.

But if I want to see the first 10 repositories again, Even if the Repositories are exactly the same as before, hasNextPage and hasPreviousPage values are not the same as before.

Ekran görüntüsü 2021-11-30 003438
Ekran görüntüsü 2021-11-30 003634

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.