@nilan @sorenbs Thanks for creating the feature request! The check point seems to have it covered 🙂 Alright, i’ll put the feature in my backlog! Thanks guys!

@schickling: thanks! Looks like some places use "Autho" instead of "Auth0"

Ah no that's just the font...

does anyone know why I have to do this on Ionic 2 + Angular 2 + Apollo Client on my

tsconfig.json

? During

ionic serve

"lib": [
      "dom",
      "es6"
    ]

But during

ionic build android

I should do this

"lib": [
      "dom",
      "es5"
    ]

And is there any work around so that I don't have to manually edit the file every time I execute the commands? If I don't change them these commands would throw error and interrupt webpack.

Maybe @kamil can help you out, @geocine! 🙂

Thank you @schickling looking forward for an answer. I understand that in the documentation this is stated

TypeScript 2.0 comes with a set of predefined type declarations.
If you’re using one of them that brings ES2015 (ES6) you should disable it, because @types/es6-shim will cause an issue with multiple types definitons.

It’s easy, just replace es6, es2015 or similar options from compilerOptions.lib for es5.

But I have to change it back when doing an

ionic serve

I am trying to use the

signinUser

mutation it is working well. However on initial page load and I click my login button without a email and password supplied I get this error on the javascript console. Do you know what is the cause of this?

error_handler.js:50 ORIGINAL EXCEPTION: this.apollo.mutate(...).toPromise is not a function

The second time I click , still with blank email and password, it will not throw that error.

Is there any login example that uses observables with error and token handling?

but when it works , either onfulfilled or onrejected code is not executed

but something is being returned

Hey @geocine. We provide quite a couple of different examples here: https://github.com/graphcool-examples

Unfortunately none with observables yet. Maybe you'd want to ask it on Stackoverflow and tag it with #graphcool? We can forward it to some angular folks!

hey @geocine, it’s quite complex with angular 2, i made it work really well though. The code is the first i wrote in the project, so some namings might seem a bit strange but maybe you’ll get something out of it https://gist.github.com/emolr/14c5967086434d8bf7f55858abddaedb I made a service though, today i would just had built it straight into the components so i didn’t need to many reducer states

@emilrmoeller thank you for your code. Ans also I realized I was missing this

import 'rxjs/add/operator/toPromise';

@emilrmoeller do you happen to know how to resolve my issue with ionic

es5(build) <-> es6(serve)

@geocine i’m not 100% sure but here’s an idea. Create an extra tsconfig.ts named

tsconfig.ionicbuild.json

(or something else) file where settings fit for building the ionic app

es5(build)

. then in package.json add a line like this

"build": “./node_modules/.bin/tsc -p src/tsconfig.ionicbuild.json”,

And run

npm run build

instead of ionic. But it sounds like something ionic would make sure to fix though

Hey guys 🙌

welcome @kitze 🙂

tnx!

I'm curious, why do the graph.cool docs suggest that the auth token should be kept in localStorage? Usually when sending an auth api call on a website it sends back a response with a header that's automatically setting a cookie with the token. Also there is usually a call for logout that will automatically log out the user on the server and send back a header that will delete the cookie automatically.

Good point @kitze. That's pretty much how you developed applications a couple of years ago (Rails etc). In the age of SPAs storing a auth token in local storage has emerged as a best practise.

Alright 👍

Have you previously had anyone complaining about storing emoji in a field? 😅 The emoji are shown like this in the data explorer (http://jmp.sh/JfmAOdh) and then rendered like this (http://jmp.sh/rOHQQrS) Any fix for this?

That's a very good point. We're already having an open issue for that: https://github.com/graphcool/console/issues/437

Unfortunately this is blocked by an external library we're using (https://github.com/spray/spray-json)

A fix is expected over the next few days: https://github.com/akka/akka-http/issues/564

Ah, okay

thanks 🙂

Hey guys