Change over to required gql tag
#168
Conversation
stubailo
changed the title
gql taggql tag
I haven't tested that yet and it probably won't work? Still need to figure this one out |
|
It will work from this branch though since it's before your other changes! Definitely have used that before. |
|
Oh cool! If that is the case it should keep working. The deploy branch doesn't change how it works locally, only moves everything to root on publish |
|
Yeah I suppose the import paths will be different for |
|
Does the PR look good? |
|
|
||
| assert.throws(() => { | ||
| queryManager.query({ | ||
| // Bamboozle TypeScript into letting us do this |
There was a problem hiding this comment.
Maybe the trowing tests should be written in JS to avoid this kind of type system coercion?
There was a problem hiding this comment.
Meh it's just one place right? I think it's great that typescript has a way of overriding types to allow us to test an edge case like this.
|
@stubailo really excited for this. It looks great to me! |
|
Going for it! |
install graphql for Meteor integration Right now, you also have to specify `apollo-server@^0.1.1`, but I think [that will change soon](apollographql/meteor-integration#26).
This will make it required to wrap all queries with:
See docs PR for details: https://github.com/apollostack/docs/pull/63
TODO:
gqlfrom a subdirectorynpm linkto test from an app