From a6c22d4f750e8baa851193857f89694e092984ed Mon Sep 17 00:00:00 2001 From: Kyle Mathews Date: Fri, 19 Jan 2018 15:14:15 -0800 Subject: [PATCH] format --- .../index.md | 2 +- docs/docs/building-apps-with-gatsby.md | 2 +- docs/docs/gatsby-starters.md | 2 +- docs/docs/querying-with-graphql.md | 2 +- .../src/create-remote-file-node.js | 2 +- packages/gatsby-source-wordpress/src/normalize.js | 8 +++++++- www/src/html.js | 7 +++++-- 7 files changed, 17 insertions(+), 8 deletions(-) diff --git a/docs/blog/2018-01-18-how-boston-gov-used-gatsby-to-be-selected-as-an-amazon-hq2-candidate-city/index.md b/docs/blog/2018-01-18-how-boston-gov-used-gatsby-to-be-selected-as-an-amazon-hq2-candidate-city/index.md index e3d87f454fe9b..8348671cf9611 100644 --- a/docs/blog/2018-01-18-how-boston-gov-used-gatsby-to-be-selected-as-an-amazon-hq2-candidate-city/index.md +++ b/docs/blog/2018-01-18-how-boston-gov-used-gatsby-to-be-selected-as-an-amazon-hq2-candidate-city/index.md @@ -10,7 +10,7 @@ Today, the team and the city scored a huge victory when Amazon announced that Bo ![Amazon Boston homepage](./amazon-boston.jpg "Boston city") -When Amazon announced in September that it was looking to build a new headquarters, bringing 50,000 jobs and billions of investment to the chosen city, Boston’s city government jumped to throw their hat in the ring. +When Amazon announced in September that it was looking to build a new headquarters, bringing 50,000 jobs and billions of investment to the chosen city, Boston’s city government jumped to throw their hat in the ring. As a technology hub, the city wanted to put their best digital foot forward, so they turned to the Boston.gov team to build a website as the city’s application — [amazon.boston.gov](http://amazon.boston.gov) . diff --git a/docs/docs/building-apps-with-gatsby.md b/docs/docs/building-apps-with-gatsby.md index 414882e0986ef..a1f3196d8c2d7 100644 --- a/docs/docs/building-apps-with-gatsby.md +++ b/docs/docs/building-apps-with-gatsby.md @@ -2,7 +2,7 @@ title: "Building apps with Gatsby" --- -Gatsby can be used to create fully dynamic apps. The default Gatsby app is made up of statically rendered pages. On this foundation, you can build what we call "hybrid" sites which adds dynamically rendered sections of pages and if needed, client-only routes. +Gatsby can be used to create fully dynamic apps. The default Gatsby app is made up of statically rendered pages. On this foundation, you can build what we call "hybrid" sites which adds dynamically rendered sections of pages and if needed, client-only routes. ## Statically rendered pages diff --git a/docs/docs/gatsby-starters.md b/docs/docs/gatsby-starters.md index eb663998bd87c..4a1bfe315734c 100644 --- a/docs/docs/gatsby-starters.md +++ b/docs/docs/gatsby-starters.md @@ -80,7 +80,7 @@ Community: * Basic components: SiteNavi, SitePost, SitePage * [gatsby-blog-starter-kit](https://github.com/dschau/gatsby-blog-starter-kit) -[(demo)](https://dschau.github.io/gatsby-blog-starter-kit/) + [(demo)](https://dschau.github.io/gatsby-blog-starter-kit/) Features: diff --git a/docs/docs/querying-with-graphql.md b/docs/docs/querying-with-graphql.md index 2ce7d7dda74da..16aeb6c3479a7 100644 --- a/docs/docs/querying-with-graphql.md +++ b/docs/docs/querying-with-graphql.md @@ -22,7 +22,7 @@ the browser when needed by your components. ## Why is GraphQL so cool? * Eliminate frontend data boilerplate — no need to worry about requesting & waiting for data. Just ask for the data you need with a GraphQL query and it'll show up when you need it -* Push frontend complexity into queries — many data transformations can be done at *build-time* within your GraphQL queries +* Push frontend complexity into queries — many data transformations can be done at _build-time_ within your GraphQL queries * It's the perfect data querying language for the often complex/nested data dependencies of modern applications * Improve performance by removing data bloat — GraphQL is a big part of why Gatsby is so fast as it enables lazy-loading the exact data in the exact form each view needs diff --git a/packages/gatsby-source-filesystem/src/create-remote-file-node.js b/packages/gatsby-source-filesystem/src/create-remote-file-node.js index 37c656f4215a6..971252e766b4c 100644 --- a/packages/gatsby-source-filesystem/src/create-remote-file-node.js +++ b/packages/gatsby-source-filesystem/src/create-remote-file-node.js @@ -27,7 +27,7 @@ module.exports = ({ url, store, cache, createNode, _auth }) => // from a previous request. const cachedHeaders = await cache.get(cacheId(url)) const headers = { - auth: _auth.htaccess_user + ':' + _auth.htaccess_pass + auth: _auth.htaccess_user + `:` + _auth.htaccess_pass, } if (cachedHeaders && cachedHeaders.etag) { headers[`If-None-Match`] = cachedHeaders.etag diff --git a/packages/gatsby-source-wordpress/src/normalize.js b/packages/gatsby-source-wordpress/src/normalize.js index 338a86e9ffe57..e1ad610f4af21 100644 --- a/packages/gatsby-source-wordpress/src/normalize.js +++ b/packages/gatsby-source-wordpress/src/normalize.js @@ -390,7 +390,13 @@ exports.mapEntitiesToMedia = entities => { } // Downloads media files and removes "sizes" data as useless in Gatsby context. -exports.downloadMediaFiles = async ({ entities, store, cache, createNode, _auth }) => +exports.downloadMediaFiles = async ({ + entities, + store, + cache, + createNode, + _auth, +}) => Promise.all( entities.map(async e => { let fileNode diff --git a/www/src/html.js b/www/src/html.js index b8128d396e699..9b2df408abac2 100644 --- a/www/src/html.js +++ b/www/src/html.js @@ -72,7 +72,7 @@ export default class HTML extends React.Component { href={`/safari-pinned-tab.svg`} color="#5bbad5" /> - +