i think i may go with react then, looks like the community is really getting behind it

That’s a fair assessment I would say. Also a big plus that the react community has a stronger uptake of GraphQL, so that will be helpful as well.

I know Dan just updated the react docs, so a good time to jump onboard 🙂

@christrotter Angular 1 and 2 are very different (the html language is kept, but is different). Angular 1 is very inefficient with the scope evaluation, DOM generation, data bindings and events. With Angular 1 the scope between components worked bad, the data binding was limited... Angular 2 is really efficient. It uses Zone.js for detect the changes and the events. It compile de view and transform it to evaluated JavaScript. The mix with Zone.js and the compilation to JS of the template and the components communications solves the initial problems of Angular 1. And... It's a more complex than Angular 1, but, when you have good knowledge about Angular 2, is really easy to program with it and is really easy to do scalable apps. I hope you have understood my explanation. I should improve my English.

Hi all. Has anyone had any luck using the react apollo client with the filter option?

Hey @robotofthefuture. Did you got the query (including the filter) to work in the playground?

It's probably me, but the request is dropping variables if they're in the filter argument.

@robotofthefuture perhaps try apollo-client@next - 0.5 is fixing some bugs of that nature

Definately working in the playground, something's happening in the graphql hoc. The GQL document shows the variable, but it seems to be dropped. I'll give that a try @sashko . Thanks!

Sorry, dropped when the HOC generates the query.

That seems to do the trick. Thanks again @sashko

yeah, we used to do some query manipulation but we stopped :]

Gotcha! Thanks for the great work.

hi everyone can wait to try graph.cool

Hey @dydycloud! I've just activated the newest batch of the early access program. You should have gotten an invite by now!

where are bugs and UX improvements typically put your github? into the feature requests repo?

no, to the github issues of the console (previously known as dashboard): www.github.com/console/issues

Hey everybody <!here|@here>! We have two updates: 1) We renamed the Dashboard to Console (and rolled out many new enhancements). You can access it here: https://console.graph.cool 2) You can now login with Github or Google. In case you want to login "the old way" please reset your password. (You should have already received an email with more details.) Please let me know if you need any help! 🏥

Anyone familiar with react? Why do we have to bind methods to react components within constructor, when they are part of the prototype? Shouldn't prototype be using this of the newly instantiated object without explicit binding?

@christrotter good question! It is due to the nature of js/js classes. Consider this snippet https://jsfiddle.net/3jm5w60j/1/ (open the console to see the result). You only need this when the methods are called from another scope. In the example you also see, that

b

is defined differently then

a

. The way

b

is defined is actually the way we define the most methods in our console react project. Then you don't need the

this.method = this.method.bind(this)

in the constructor anymore.

@christrotter in case you use ES6 you just de

::this.method

and that’s the same as

this.method.bind(this)

@tim2 @rene thank you both.

Hi, I'm just a beginner but I'm going to be on an open source project at webdev.camp (code bootcamp) that I think this would be great for! How do I try it? Thanks!

Hi @scripttease. You can just signup here and get started: https://console.graph.cool/signup

hi everyone! @nilan thanks for inviting me:)

Welcome Alex 🙂

hey - anyone using

react-relay-network-layer

to connect to their graphql server? https://github.com/nodkz/react-relay-network-layer/

in particular the auth middleware?

Oh that looks interesting, no we haven't used it yet. Maybe somebody else? 🙂

Yeah its useful as it handles setting Authorization headers on each request and refreshing token when

401

is received