profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/meganesu/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

gatsbyjs/gatsby 50994

Build blazing fast, modern apps and websites with React

meganesu/gatsby-intro-workshop 2

The code for the curriculum companion site for the Getting Started with Gatsby workshop (from GatsbyConf in March 2021).

meganesu/gatsby-intro-workshop-example-site-with-v3 2

This is the example site built by following the Getting Started with Gatsby workshop at GatsbyConf 2021.

meganesu/fifty-nifty 1

Bucket List Tracker: Visit all 50 states

arinclement/friendship-remider 0

Hackatines Day project

gatsbyjs/tutorial-example 0

The example project built by following the Gatsby Tutorial: https://gatsbyjs.com/docs/tutorial

meganesu/a11y-crash-course 0

An outline of free online resources to learn about web accessibility

push eventgatsbyjs/gatsby

Megan Sullivan

commit sha a1b485e033d0f19cd13edc4671d46177c811014c

docs(tutorial): fix typo in part 6

view details

Megan Sullivan

commit sha 96d5c00506172f4d682390e51f4067e3dcaea4f4

docs(tutorial): WIP outline rough structure of part 7

view details

Megan Sullivan

commit sha d1974bc1e23dccade6097dd678cd866904f21c66

docs(tutorial): outline rough structure of What's Next

view details

push time in 20 hours

pull request commentcontentful/starter-gatsby-blog

Update to Gatsby v3, new `gatsby-plugin-image`; design rinse

@fk tested this out and had some difficulty setting up a space with a matching content model so that I could run it locally.

Maybe adding a note like this to end of the "Set up of the needed content model and create a configuration file" section of the README would help:

**Note:** If you don't have an existing content model, you can automatically generate a new Space with a Content model and test data by using the `contentful guide` CLI command from the [official Contentful getting started guide](https://www.contentful.com/developers/docs/tutorials/general/get-started/).

(Tried to make the change myself but I don't have permission to commit 😁 )

fk

comment created time in a day

Pull request review commentcontentful/starter-gatsby-blog

Update to Gatsby v3, new `gatsby-plugin-image`; design rinse

 import React from 'react' import { Link } from 'gatsby'-import Img from 'gatsby-image'+import { GatsbyImage } from 'gatsby-plugin-image' -import styles from './article-preview.module.css'+import Container from './container'+import Tags from './tags'+import * as styles from './article-preview.module.css' -export default ({ article }) => (-  <div className={styles.preview}>-    <Img alt="" fluid={article.heroImage.fluid} />-    <h3 className={styles.previewTitle}>-      <Link to={`/blog/${article.slug}`}>{article.title}</Link>-    </h3>-    <small>{article.publishDate}</small>-    <p-      dangerouslySetInnerHTML={{-        __html: article.description.childMarkdownRemark.html,-      }}-    />-  </div>-)+const ArticlePreview = ({ posts }) => {+  if (!posts) return null+  if (!Array.isArray(posts)) return null++  return (+    <Container>+      <ul className={styles.articleList}>+        {posts.map((post) => {+          return (+            <li key={post.slug}>+              <Link to={`/blog/${post.slug}`} className={styles.link}>

How strongly do you feel about having the entire card contents be inside of this link? Asking bc when using a screen reader, it'll read out the entire contents as the link text. It also doesn't include punctuation between things like the title, description, date, and tags, so it just reads them all out in one breath.

We could make just the h2 a link instead, so that the rest of the elements will be read out separately

Screen Shot 2021-08-04 at 11 12 56 AM

fk

comment created time in a day

PullRequestReviewEvent

push eventmeganesu/TIL

Megan Sullivan

commit sha c778984dfaed6061a6abefd840c5350a9206cce4

add designing an accessible user experience notes

view details

push time in 2 days

push eventmegan-testing-things/my-first-gatsby-site

Megan Sullivan

commit sha df43185a736fb60818f7e04a46604b6e1cc718a4

feat(part-6): create blog post page template

view details

Megan Sullivan

commit sha 853906fc0300458b6b760967c213d3000d4a817f

feat(part-6): update route to include /blog path parameter

view details

Megan Sullivan

commit sha cc4ceac9bd673ec266d4f6b4b9c11725c82815c7

feat(part-6): render post contents in blog post page template

view details

Megan Sullivan

commit sha ef39f9b348cee7a82fe62d25470eefce0f687b14

feat(part-6): update blog page to link to each post

view details

push time in 3 days

PullRequestReviewEvent

startedbitprj/Intro-To-Serverless

started time in 3 days

startedbitprj/counselor

started time in 3 days

push eventmeganesu/meganesu.github.io

Travis CI User

commit sha d0094f2cc80bc2ff4ab8db000a5e614c85d90b74

content: update publish date for retrieval practice (469fadcfc349e70eaf7f7fbd5a68c700d27c4870)

view details

push time in 4 days

delete branch meganesu/personal-site-v2

delete branch : content/retrieval-practice

delete time in 4 days

push eventmeganesu/personal-site-v2

Megan Sullivan

commit sha 7c9509e9213b4c850beed6152f92d8a930840b6e

content: copy over contents from retrieval practice slide deck

view details

Megan Sullivan

commit sha bede3e619fc35aa9b1a1fd35b37c8a2a2019f2b9

content: add collapsible component (no styles)

view details

Megan Sullivan

commit sha fdeb9192b2076f52771a1909cc58c22eca3dcc26

feat: create calloutbox component

view details

Megan Sullivan

commit sha 13f5d5ff4769598404aadad9eabfa660111ea6d3

feat: style collapsible component

view details

Megan Sullivan

commit sha 9d30b155b5d26c3686a8feacd2ba752ccd80e578

chore: update 'illustration' tag to 'illustrated'

view details

Megan Sullivan

commit sha f26c08c73cec471db8428dfbddf0c119aa5eefdc

content: remove unused SVG for retrieval practice post

view details

Megan Sullivan

commit sha 08e396e4778c02365f43f80f18b8795623ef6c93

chore: update old blog posts to use calloutbox component instead of misusing blockquote

view details

Megan Sullivan

commit sha 6b12966d43cf6ea4d643eb837fc30135a0b02fd5

feat: update styles for blockquotes

view details

Megan Sullivan

commit sha 8a3ba0b0a4e9f9fc48d66764389b39318997a42c

content: update retrieval practice images; copy edits

view details

Megan Sullivan

commit sha b8a09510384192c211d6bf9f6bbab950d7b3a39f

content: finish alt text and copy edits for retrieval practice

view details

Megan Sullivan

commit sha 469fadcfc349e70eaf7f7fbd5a68c700d27c4870

content: update publish date for retrieval practice

view details

push time in 4 days

push eventmeganesu/personal-site-v2

Megan Sullivan

commit sha 3dcdb1a9ad004d9b28b9a1e84120354d06956ee5

content: update publish date for retrieval practice

view details

push time in 4 days

push eventmeganesu/personal-site-v2

Megan Sullivan

commit sha 146c5270aff91c6496825307191d6804695e305e

content: finish alt text and copy edits for retrieval practice

view details

push time in 4 days

push eventmeganesu/personal-site-v2

Megan Sullivan

commit sha e2d0dd235f94fae12b9b3a6e56486c3044d3a050

content: update retrieval practice images; copy edits

view details

push time in 4 days

push eventmeganesu/personal-site-v2

Megan Sullivan

commit sha a9ce9d09b1001e0f872ef64bbb49b3f771568275

chore: update old blog posts to use calloutbox component instead of misusing blockquote

view details

Megan Sullivan

commit sha d38479aa3b0ec1112d52a1e3388177d844dbb973

feat: update styles for blockquotes

view details

push time in 4 days

push eventgatsbyjs/gatsby

Vladimir Razuvaev

commit sha 9b427936752ec0b107b36331f444366987355fbb

fix(gatsby): correct results for multiple range filters with indexes (#32406) * fix(gatsby): correct results when using multiple range filters with indexes * fix tests * fix handling of skip/limit with indexes * fix incorrect limit

view details

Michal Piechowiak

commit sha d8479b2fa64352c0cb9f1c8e870812e75178695f

chore(release): Publish next pre-minor - babel-plugin-remove-graphql-queries@3.12.0-next.0 - babel-preset-gatsby-package@1.12.0-next.0 - babel-preset-gatsby@1.12.0-next.0 - create-gatsby@1.12.0-next.0 - gatsby-admin@0.22.0-next.0 - gatsby-cli@3.12.0-next.0 - gatsby-codemods@2.12.0-next.0 - gatsby-core-utils@2.12.0-next.0 - gatsby-cypress@1.12.0-next.0 - gatsby-design-tokens@3.12.0-next.0 - gatsby-dev-cli@3.12.0-next.0 - gatsby-graphiql-explorer@1.12.0-next.0 - gatsby-image@3.12.0-next.0 - gatsby-legacy-polyfills@1.12.0-next.0 - gatsby-link@3.12.0-next.0 - gatsby-page-utils@1.12.0-next.0 - gatsby-plugin-benchmark-reporting@1.12.0-next.0 - gatsby-plugin-canonical-urls@3.12.0-next.0 - gatsby-plugin-catch-links@3.12.0-next.0 - gatsby-plugin-coffeescript@3.12.0-next.0 - gatsby-plugin-create-client-paths@3.12.0-next.0 - gatsby-plugin-cxs@3.12.0-next.0 - gatsby-plugin-emotion@6.12.0-next.0 - gatsby-plugin-facebook-analytics@3.12.0-next.0 - gatsby-plugin-feed@3.12.0-next.0 - gatsby-plugin-flow@2.12.0-next.0 - gatsby-plugin-fullstory@3.12.0-next.0 - gatsby-plugin-gatsby-cloud@2.12.0-next.0 - gatsby-plugin-glamor@3.12.0-next.0 - gatsby-plugin-google-analytics@3.12.0-next.0 - gatsby-plugin-google-gtag@3.12.0-next.0 - gatsby-plugin-google-tagmanager@3.12.0-next.0 - gatsby-plugin-graphql-config@0.21.0-next.0 - gatsby-plugin-image@1.12.0-next.0 - gatsby-plugin-jss@3.12.0-next.0 - gatsby-plugin-layout@2.12.0-next.0 - gatsby-plugin-less@5.12.0-next.0 - gatsby-plugin-lodash@4.12.0-next.0 - gatsby-plugin-manifest@3.12.0-next.0 - gatsby-plugin-mdx@2.12.0-next.0 - gatsby-plugin-netlify-cms@5.12.0-next.0 - gatsby-plugin-netlify@3.12.0-next.0 - gatsby-plugin-no-sourcemaps@3.12.0-next.0 - gatsby-plugin-nprogress@3.12.0-next.0 - gatsby-plugin-offline@4.12.0-next.0 - gatsby-plugin-page-creator@3.12.0-next.0 - gatsby-plugin-postcss@4.12.0-next.0 - gatsby-plugin-preact@5.12.0-next.0 - gatsby-plugin-preload-fonts@2.12.0-next.0 - gatsby-plugin-react-css-modules@3.12.0-next.0 - gatsby-plugin-react-helmet@4.12.0-next.0 - gatsby-plugin-remove-trailing-slashes@3.12.0-next.0 - gatsby-plugin-sass@4.12.0-next.0 - gatsby-plugin-schema-snapshot@2.12.0-next.0 - gatsby-plugin-sharp@3.12.0-next.0 - gatsby-plugin-sitemap@4.8.0-next.0 - gatsby-plugin-styled-components@4.12.0-next.0 - gatsby-plugin-styled-jsx@4.12.0-next.0 - gatsby-plugin-styletron@6.12.0-next.0 - gatsby-plugin-stylus@3.12.0-next.0 - gatsby-plugin-subfont@3.12.0-next.0 - gatsby-plugin-twitter@3.12.0-next.0 - gatsby-plugin-typescript@3.12.0-next.0 - gatsby-plugin-typography@3.12.0-next.0 - gatsby-plugin-utils@1.12.0-next.0 - gatsby-react-router-scroll@4.12.0-next.0 - gatsby-recipes@0.23.0-next.0 - gatsby-remark-autolink-headers@4.9.0-next.0 - gatsby-remark-code-repls@5.9.0-next.0 - gatsby-remark-copy-linked-files@4.9.0-next.0 - gatsby-remark-custom-blocks@3.12.0-next.0 - gatsby-remark-embed-snippet@6.9.0-next.0 - gatsby-remark-graphviz@3.9.0-next.0 - gatsby-remark-images-contentful@4.9.0-next.0 - gatsby-remark-images@5.9.0-next.0 - gatsby-remark-katex@5.9.0-next.0 - gatsby-remark-prismjs@5.9.0-next.0 - gatsby-remark-responsive-iframe@4.9.0-next.0 - gatsby-remark-smartypants@4.9.0-next.0 - gatsby-source-contentful@5.12.0-next.0 - gatsby-source-drupal@4.12.0-next.0 - gatsby-source-faker@3.12.0-next.0 - gatsby-source-filesystem@3.12.0-next.0 - gatsby-source-graphql@3.12.0-next.0 - gatsby-source-hacker-news@3.12.0-next.0 - gatsby-source-lever@3.12.0-next.0 - gatsby-source-medium@3.12.0-next.0 - gatsby-source-mongodb@3.12.0-next.0 - gatsby-source-npm-package-search@3.12.0-next.0 - gatsby-source-shopify@5.4.0-next.0 - gatsby-source-wikipedia@3.12.0-next.0 - gatsby-source-wordpress@5.12.0-next.0 - gatsby-telemetry@2.12.0-next.0 - gatsby-transformer-asciidoc@2.12.0-next.0 - gatsby-transformer-csv@3.12.0-next.0 - gatsby-transformer-documentationjs@5.12.0-next.0 - gatsby-transformer-excel@3.12.0-next.0 - gatsby-transformer-hjson@3.12.0-next.0 - gatsby-transformer-javascript-frontmatter@3.12.0-next.0 - gatsby-transformer-javascript-static-exports@3.12.0-next.0 - gatsby-transformer-json@3.12.0-next.0 - gatsby-transformer-pdf@2.12.0-next.0 - gatsby-transformer-react-docgen@6.12.0-next.0 - gatsby-transformer-remark@4.9.0-next.0 - gatsby-transformer-screenshot@3.12.0-next.0 - gatsby-transformer-sharp@3.12.0-next.0 - gatsby-transformer-sqip@3.12.0-next.0 - gatsby-transformer-toml@3.12.0-next.0 - gatsby-transformer-xml@3.12.0-next.0 - gatsby-transformer-yaml@3.12.0-next.0 - gatsby-worker@0.3.0-next.0 - gatsby@3.12.0-next.0

view details

Megan Sullivan

commit sha cfce9ebd820f5c1b635c4ef8112b55aa87b9b5bd

docs(tutorial): improve a11y of layout component (#32539) * docs(tutorial): improve a11y of layout component * docs(tutorial): add tip about unique query names

view details

Brent Jackson

commit sha 15100915364ad6ea538d5384076260935e7967a6

docs: replace graphiql playgrounds in GraphQL Reference with code blocks (#32543) * chore(docs): replace GraphiQL iframes with code blocks * chore(docs): update copy in GraphQL reference * Update docs/docs/graphql-reference.md Co-authored-by: Florian Kissling <21834+fk@users.noreply.github.com> * Update docs/docs/graphql-reference.md Co-authored-by: Florian Kissling <21834+fk@users.noreply.github.com> * chore(docs): fix typo * docs: update gatsbyjs.com link to use relative path * docs: fix grammar, and make link text descriptive (for a11y) * docs: add missing comma * docs: clean up heading structure Co-authored-by: Florian Kissling <21834+fk@users.noreply.github.com> Co-authored-by: Megan Sullivan <megan@gatsbyjs.com>

view details

Megan Sullivan

commit sha f84dff6694908b0e86fa983e51a9ea8dfd16e567

Merge branch 'master' into tutorial/part-7

view details

Megan Sullivan

commit sha 45e3f9288447980cbc5698a6cf96dd633beda9d4

docs(tutorial): fix typo in part 2

view details

push time in 4 days

push eventmeganesu/personal-site-v2

Megan Sullivan

commit sha d7cc02e7621bda4ec34787cb03c66517bad05e7c

content: remove unused SVG for retrieval practice post

view details

push time in 5 days

push eventmeganesu/personal-site-v2

Megan Sullivan

commit sha 4a475579d523b2aa25a70966f7f795ced241e068

chore: update 'illustration' tag to 'illustrated'

view details

push time in 5 days

push eventmeganesu/personal-site-v2

Megan Sullivan

commit sha 56d712850b16b3f3dd261c7491032397fa87b7d6

feat: create calloutbox component

view details

Megan Sullivan

commit sha 06bd68fcb3136a1d6419b257c622390da1b214f0

feat: style collapsible component

view details

push time in 5 days

issue closedthe-collab-lab/tcl-28-smart-shopping-list

5. As a user, I want to join an existing shopping list so I can share a shopping list with another person.

Tokens can be shared with other users to allow them to co-manage a given list.

Joining an existing list consists of the following:

  • User enters an existing token
  • Save the token to localStorage
  • Show the user the existing list

AC:

  • When the user does not already have a token in localStorage, on the onboarding/home screen, a simple form is displayed that allows the user to enter a token
  • Entering the token and hitting submit saves the token to localStorage, effectively giving them joint control of the list
  • On submit, show an error if the token does not exist
  • If they get an error message, allow them to try again or create a new list

Notes:

  • As of this story, the welcome/home screen will be feature complete, as reflected in this wireframe: https://github.com/the-collab-lab/smart-shopping-list/blob/main/_resources/wireframes/welcome-screen.png
  • For accessibility reasons, use a <label> tag for the share token field.
  • You can assume that users will only be sharing a token if the list has actual items on it. So, let's say I create a New Shopping List, but never add any items to it, and haven't saved that particular token to Firestore, we can assume that's a list that doesn't exist.
  • If you would like, you can save the token to Firestore immediately when creating a list, and then a user would be able to share an empty list (see issue 5).

closed time in 5 days

dgorley

create barnchmeganesu/personal-site-v2

branch : content/retrieval-practice

created branch time in 6 days

push eventgatsbyjs/gatsby

Brent Jackson

commit sha 15100915364ad6ea538d5384076260935e7967a6

docs: replace graphiql playgrounds in GraphQL Reference with code blocks (#32543) * chore(docs): replace GraphiQL iframes with code blocks * chore(docs): update copy in GraphQL reference * Update docs/docs/graphql-reference.md Co-authored-by: Florian Kissling <21834+fk@users.noreply.github.com> * Update docs/docs/graphql-reference.md Co-authored-by: Florian Kissling <21834+fk@users.noreply.github.com> * chore(docs): fix typo * docs: update gatsbyjs.com link to use relative path * docs: fix grammar, and make link text descriptive (for a11y) * docs: add missing comma * docs: clean up heading structure Co-authored-by: Florian Kissling <21834+fk@users.noreply.github.com> Co-authored-by: Megan Sullivan <megan@gatsbyjs.com>

view details

push time in 6 days

delete branch gatsbyjs/gatsby

delete branch : docs-fix-gql-reference

delete time in 6 days

PR merged gatsbyjs/gatsby

Reviewers
Docs: fix GraphQL Reference status: triage needed

Description

This replaces the GraphiQL iframes in the GraphQL Reference section with static code blocks. The current setup, using Gatsby Preview will stop working once the new Preview experience is fully rolled out.

I made some light copy edits to avoid language related to the interactive iframes and am looking for proofreading and editing suggestions.

Related Issues

Reported internally [ch32387]

+613 -214

0 comment

1 changed file

jxnblk

pr closed time in 6 days

PullRequestReviewEvent

Pull request review commentgatsbyjs/gatsby

Docs: fix GraphQL Reference

 title: GraphQL Query Options Reference  ## Intro -This page will walk you through a series of GraphQL queries, each designed to demonstrate a particular feature of GraphQL. You'll be querying the _real_ schema used on [graphql-reference example](https://github.com/gatsbyjs/gatsby/tree/master/examples/graphql-reference) so feel free to experiment and poke around the innards of the site! You can also open the [CodeSandbox version](https://codesandbox.io/s/github/gatsbyjs/gatsby/tree/master/examples/graphql-reference) ([Direct link to GraphiQL](<https://graphql-reference-1124782374.gtsb.io/___graphql?query=%7B%0A%20%20site%20%7B%0A%20%20%20%20siteMetadata%20%7B%0A%20%20%20%20%20%20title%0A%20%20%20%20%20%20description%0A%20%20%20%20%7D%0A%20%20%7D%0A%20%20books%3A%20allMarkdownRemark(filter%3A%20%7Bfrontmatter%3A%20%7Btitle%3A%20%7Bne%3A%20%22%22%7D%7D%7D)%20%7B%0A%20%20%20%20totalCount%0A%20%20%20%20edges%20%7B%0A%20%20%20%20%20%20node%20%7B%0A%20%20%20%20%20%20%20%20frontmatter%20%7B%0A%20%20%20%20%20%20%20%20%20%20title%0A%20%20%20%20%20%20%20%20%20%20date(fromNow%3A%20true)%0A%20%20%20%20%20%20%20%20%20%20author%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20id%0A%20%20%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%0A%20%20%7D%0A%20%20authors%3A%20allAuthorYaml%20%7B%0A%20%20%20%20totalCount%0A%20%20%20%20edges%20%7B%0A%20%20%20%20%20%20node%20%7B%0A%20%20%20%20%20%20%20%20id%0A%20%20%20%20%20%20%20%20bio%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%0A%20%20%7D%0A%7D%0A>)) of it.+This page will walk you through a series of GraphQL queries, each designed to demonstrate a particular feature of GraphQL.+These examples will work on the _real_ schema used on [graphql-reference example](https://github.com/gatsbyjs/gatsby/tree/master/examples/graphql-reference).+You can run this example locally to experiment and poke around the innards of the site!+You can also open the [CodeSandbox version](https://codesandbox.io/s/github/gatsbyjs/gatsby/tree/master/examples/graphql-reference) of it. -You'll be using GraphiQL, an interactive editor you can also use [while building your Gatsby site](/docs/tutorial/part-five/#introducing-graphiql).+For more information, read about [why Gatsby uses GraphQL](/docs/why-gatsby-uses-graphql/) and [how to use GraphiQL][] in any Gatsby site. -For more information, read about [why Gatsby uses GraphQL](/docs/why-gatsby-uses-graphql/).+[how to use graphiql]: /docs/tutorial/part-4/#use-graphiql-to-explore-the-data-layer-and-write-graphql-queries  ## Basic query -Start with the basics, pulling up the site `title` from your `gatsby-config.js`'s `siteMetadata`. Here the query is on the left and the results are on the right.+Start with the basics, pulling up the site `title` from your `gatsby-config.js`'s `siteMetadata`. -<iframe-  title="A basic query"-  src="https://graphql-reference-1124782374.gtsb.io/___graphql?query=%7B%0A%20%20site%20%7B%0A%20%20%20%20siteMetadata%20%7B%0A%20%20%20%20%20%20title%0A%20%20%20%20%7D%0A%20%20%7D%0A%7D%0A&explorerIsOpen=false"-  width="600"-  height="400"-  loading="lazy"-></iframe>+```graphql+{+  site {+    siteMetadata {+      title+    }+  }+}+``` -Try editing the query to include the `description` from `siteMetadata`. When typing in the query editor you can use `Ctrl + Space` to see autocomplete options and `Ctrl + Enter` to run the current query.+In the GraphiQL editor, try editing the query to include the `description` from `siteMetadata`. When typing in the query editor you can use `Ctrl + Space` to see autocomplete options and `Ctrl + Enter` to run the current query.  ## A longer query  Gatsby structures its content as collections of `nodes`, which are connected to each other with `edges`. In this query you ask for the total count of plugins in this Gatsby site, along with specific information about each one. -<iframe-  title="A longer query"-  src="https://graphql-reference-1124782374.gtsb.io/___graphql?query=%7B%0A%20%20allSitePlugin%20%7B%0A%20%20%20%20totalCount%0A%20%20%20%20edges%20%7B%0A%20%20%20%20%20%20node%20%7B%0A%20%20%20%20%20%20%20%20name%0A%20%20%20%20%20%20%20%20version%0A%20%20%20%20%20%20%20%20packageJson%20%7B%0A%20%20%20%20%20%20%20%20%20%20description%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%0A%20%20%7D%0A%7D%0A&explorerIsOpen=false"-  width="600"-  height="400"-  loading="lazy"-></iframe>+```graphql+{+  allSitePlugin {+    totalCount+    edges {+      node {+        name+        version+        packageJson {+          description+        }+      }+    }+  }+}+``` -Try using the editor's autocomplete (`Ctrl + Space`) to get extended details from the `packageJson` nodes.+In the GraphiQL editor, try using the editor's autocomplete (`Ctrl + Space`) to get extended details from the `packageJson` nodes.  If you're using Gatsby version `2.2.0` or later, you can remove `edges` and `node` from your query and replace it with `nodes`. The query will still work and the returned object will reflect the `nodes` structure.

I'm thinking since this is the v3 version of the docs, maybe we can get rid of the first example and just use the nodes field instead of edges.nodes. And then if they're on v2 of the docs, they'll still see the old version.

Although now I'm wondering whether we should cherry-pick this commit (once this PR is merged) on the v2 docs branch, so that people looking at those docs won't see the broken GraphiQL embeds either. And in that case, we should keep this edges.nodes bit until after the cherry-pick is applied. Thoughts?

jxnblk

comment created time in 6 days