since theres just so much to learn its hard to filter what tech I might be interested in, so I would agree that education and awareness are the two most important things the community can share right now

And I agree with @notrab. You guys’ efforts in the GraphQL community has been a huge part of my success in learning it. Thanks for taking the time to make such great content!

I can recommend the apollo / graphcool tutorial on howtographql - I'm already using apollo for queries and mutations but I picked up a few useful bits of info. I hadn't used subscriptions when I went through it and it does a really good job of explaining how they work.

Thanks so much everyone <!here|@here> ❤️ If you want to help someone to get started with GraphQL or want to improve your understanding in a certain area, hopefully now you have a good resouce to share 🙂 For example, the

graphql-js

track was SUPER helpful to improve my understanding of how backend and frontend are connected 🙂

Hey guys it has been a while since I checked in, wanted to ask if email / password auth has been extended to support password changes / email verification / email changes etc… I believe there was a github issue for this, but I can’t seem to find it anymore

@nilan paste the HackerNews link here pls 🙂

That is a badass tutorial. It provides the same conclusion that I came to - it's almost impossible to easily build a GraphQL server withould GraphCool 😉 I'd be writing Resolvers day and night otherwise. Or use the only reasonable opensource integrated solution I found (https://github.com/postgraphql/postgraphql) which works only with Postgres, and good luck when I hit the whatever limitations it might have..

@nilan this is great to share with the co-workers and explain better the advantages! KUDOS and Thank you!

Hi there!

Interested in hearing opinions on Relay vs Apollo.

anyone has a quick hint how to use updateOrCreate… mutation?

hey guys, is there a way to view my graph.cool metrics, like how many request I have done in the month, etc?

hey team 👋 is there a way to apply a similar permission query across multiple types? Our permission logic is largely the same across types (e.g. the user must exist for the organisation that owns this resource). If I wanted to make a change, do I need to change it for each type across all operations from the web UI?

Hey everyone <!here|@here> 👋 today, we launched the biggest learning resource on GraphQL - How to GraphQL - and it's now listed on Hacker News 🎉 Please help us spread the word by upvoting and commenting 🙏 You can find the post here (search for How to GraphQL): https://news.ycombinator.com/newest

hey team, i'm running the relay modern tutorial and can't seem to access relay-compiler

one more question this eve 😅 is this the set-up you guys require for authentication over WebSockets with Apollo? http://dev.apollodata.com/react/subscriptions.html#authentication. I'm passing the user's JWT as so:

connectionParams: {
  authToken: JWT,
}

and can see that the

SubscriptionClient

is being initialised with the JWT. However, I'm seeing

message: "Insufficient Permissions"

when the subscription is triggered. I'm just using

Authentication required

as the rule right now, without a permission query.

Hi Guys. Trying some thing out with apollo, subscriptions and vuejs. Everything is working fine, only i'm not sure how to use orderBy filter in combination with subscriptions. The new items added are ignoring the orderby filter *drops in some code *

<script>
import gql from 'graphql-tag';

// GraphQL query
const ClientQuery = gql`
  query allClients {
    allClients(orderBy: createdAt_DESC) {
      id,
      name
    }
  }`;

export default {
  data() {
    return {
      msg: 'Welcome  2 to Your Vue.js App',
      loading: 0,
      allClients: {},
    };
  },
  // Apollo GraphQL
  apollo: {
    allClients() {
      return {
        query: ClientQuery,
        loadingKey: 'loading',
      };
    },
  },
  mounted() {
    // Query runs to start the subscription
    const subQuery = gql`
      subscription {
        Client(filter: {
          mutation_in: [CREATED]
        }) {
          node {
            id,
            name
          }
        }
      }`;
    this.clientsSubscription = this.$apollo.queries.allClients.subscribeToMore({
      document: subQuery,
      // Mutate the previous result
      updateQuery: (previousResult, { subscriptionData }) => ({
        allClients: [
          ...previousResult.allClients,
          // Add the new tag
          subscriptionData.data.Client.node,
        ],
      }),
    });
  },
};
</script>

best practice for backing up my data?

can I give you guys money for that

lol

4x daily increment with a fade-out TTL? after 24 hours it only keeps 1 copy per day, after 7 days it only keeps 1 copy per week, totally dead in 30 days

I’m getting the error

Directive 'include' may not be used on fragment definition

when creating a new

request pipeline

function in the console

hey guys, every so often im getting a websocket closed before connection established... can't replicate consistently but at times using the system Ill see the subs stop working and get this

any ideas

@nilan no auth

just doing a test runthrough so leavin ti all open in case thats misconfigured

Hey all, I suppose this is more a graphql question, but… if I am sending multiple mutations in a request, can I use the response variables in the second mutation generated by the first?

@auser try taking a look at the connected mutations. I’m assuming this is something like you have a related type that you want created at the same time as the first type, and need the ID for that? You can pass in the values of the related type within the mutation args, and graph.cool will create the related object as well.

I did it independently in JS for the time being — thanks @phil — I’ll check that out

hello everyone, how can I send the authorization token in the graphql query?