Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[1.0] Relay Compiler #912

Merged
merged 34 commits into from
May 4, 2017
Merged

[1.0] Relay Compiler #912

merged 34 commits into from
May 4, 2017

Conversation

KyleAMathews
Copy link
Contributor

This is @jquense's PR #876 with a few fixes I found while trying out our new swanky Relay Compiler integration on my blog.

@gatsbybot
Copy link
Collaborator

gatsbybot commented May 4, 2017

Deploy preview ready!

Built with commit 2de79bd

https://deploy-preview-912--using-drupal.netlify.com

@gatsbybot
Copy link
Collaborator

gatsbybot commented May 4, 2017

Deploy preview ready!

Built with commit 2de79bd

https://deploy-preview-912--gatsbyjs.netlify.com

@gatsbybot
Copy link
Collaborator

gatsbybot commented May 4, 2017

Deploy preview ready!

Built with commit 2de79bd

https://deploy-preview-912--gatsbygram.netlify.com

echo "=== find graphql packages"

find node_modules -name graphql
echo "=== END find graphql packages"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i am hoping this is better after the next npm publish since everything has been moved to peer deps :/

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did that already... :-\

Can't reproduce locally — it's giving me a weird graphql error where it says the "schema" isn't the correct type.

Breaking out Docker...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What use do you see to having graphql set as a peerDependency? I'm thinking about just removing it because plugins have to use the same version of GraphQL as Gatsby's core package.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it should ensure a single instance of it given a fresh install but you know...npm

Maybe the best approach is actually to expose graphql to plugins like babel does for babel.types. like pass in the `graphql' object

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ooo that's an interesting idea.

@KyleAMathews KyleAMathews merged this pull request into 1.0 May 4, 2017
@KyleAMathews
Copy link
Contributor Author

Woot! And it's in!

@KyleAMathews
Copy link
Contributor Author

@jquense hrrmm... probably should have squashed and merged this instead of squashing as now it says I wrote all of this code :-(

@KyleAMathews
Copy link
Contributor Author

actually, I'll rewrite the commit to make you the author

@jquense
Copy link
Contributor

jquense commented May 4, 2017

Hehe no worries glad it's in!

KyleAMathews pushed a commit that referenced this pull request May 4, 2017
* Relay integration

* what is the deal with eslint

* gatsbygram update

* Hacker News example

* Drupal example

* bonus dependency

* Missed adding this

* Actually format example code

* update dependencies

* Get types for nested arguments + handle argument lists

* Add missing babel-runtime dependency

* Try removing hoisting to see if that fixes site builds

* debugging

* Updates from @jquense's changes

* Set websites to use 'canary' versions of websites so always download latest

* Add required yaml-loader

* Remove yarn.locks from example sites as we always want to install the latest code to catch errors early

* Update www for the new relay compiler

* Lengthen debounce so stuff can really finish

* Make paths to bin relative

* Restore lerna hoisting

* Add error and quit if a query name is missing

* Dunno if this helps but...

* Fix version string

* debugging...

* More info

* Follow links

* Add netlify.toml to set yarn version

* Turned out not what we want

* Get around permission error on Netlify

* Don't overwrite the Gatsby bin directory or it'll stop working

* Remove this workaround

* Remove debuggin
@KyleAMathews
Copy link
Contributor Author

no no, whenever people run 'git blame' I want them to come find you not me!

@KyleAMathews
Copy link
Contributor Author

anyways, fixed it already bb772f8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants