-
Notifications
You must be signed in to change notification settings - Fork 12
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
Feature/whats new #19
base: feature/whatsNew
Are you sure you want to change the base?
Feature/whats new #19
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a few minor comments. Also - can you raise this PR into gh-pages
branch instead? feature/whatsNew
was a feature we started but never finalized + never merged (it's not ready to merge).
You can create your own feature branch from gh-pages (call it say, feature/jamesChanges
, or whatever), and merge into gh-pages. Thanks!
layout: default | ||
title: Best Practices | ||
nav_order: 4 | ||
parent: GraphQL Concepts |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just want to clarify, do you want this under GraphQL Concepts, or under FAQ?
If we want it under GraphQL Concepts, can we just move this file into the directory graphql-concepts/
(just for organization)? It's currently in the faq/
dir.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's move it under FAQ, makes most sense to me
Instead of specifying a list of field names we recommend creating a fragment as a best practice once and reuse it everywhere. This makes your queries modular and easy to understand. [Read more about fragments here](../../graphql-concepts/other-concepts/#fragments) | ||
|
||
|
||
## Error Handling |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume the intent was to remove Error Handling from this page (into its own page), right? We should remove it from here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, was trying to move it, sorry!
parent: GraphQL Concepts | ||
--- | ||
|
||
## Best Practices |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ditto as above, should remove this top section (Best Practices), and leave only Error Handling bottom section (assuming that was the intent here)
parent: GraphQL Concepts | ||
--- | ||
|
||
## Best Practices |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ditto as above, should remove this top section (Best Practices), and leave only Error Handling bottom section (assuming that was the intent here)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was trying to create two separate pages, one for errors and one for best practices - sorry I am still learning this
James' updates