Fix lint

src/ReactSEOMetaTags.tsx

@@ -44,7 +44,7 @@ export class ReactSEOMetaTags extends React.PureComponent<ReactSEOMetaTagsProps>
   /**
    * https://developers.facebook.com/docs/sharing/webmasters/
    * http://ogp.me/
-   * @param props 
+   * @param props
    */
   renderFacebook({ url, title, description, image, site, facebookAppId }: CombinedProps<FacebookProps>) {
     return ([

src/SchemaOrg.ts

@@ -18,18 +18,17 @@ import {
  * @param props
  */
 const generateSiteJSONLD = ({ url, title, description, author } : WebsiteProps) => (
-  {
-    '@context': 'http://schema.org',
-    '@type': 'WebSite',
-    name: title,
-    url,
-    description,
-    author: {
-      '@type': author && author.schemaType,
-      name: author && author.name
-    }
+{
+  '@context': 'http://schema.org',
+  '@type': 'WebSite',
+  name: title,
+  url,
+  description,
+  author: {
+    '@type': author && author.schemaType,
+    name: author && author.name
   }
-)
+})
 
 /**
  * This schema is a bit tricker one but it's simply a showcase of your page on say Google results.
@@ -38,7 +37,7 @@ const generateSiteJSONLD = ({ url, title, description, author } : WebsiteProps)
  * @param props
  */
 const generateBreadcrumbList = ({ url, title, image } : WebsiteProps & BlogPostProps) => (
-  {
+{
   '@context': 'http://schema.org',
   '@type': 'BreadcrumbList',
   itemListElement: [
@@ -58,44 +57,46 @@ const generateBreadcrumbList = ({ url, title, image } : WebsiteProps & BlogPostP
  * This is a general BlogPosting schema which covers quite a few attributes.
  * @param props
  */
-const generateBlogPosting = ({ url, title, description, image, datePublished, dateModified, tags, site, author, organization } : WebsiteProps & BlogPostProps) => (
-{
-  '@context': 'http://schema.org',
-  '@type': 'BlogPosting',
-  url,
-  name: title,
-  headline: title,
-  keywords: tags,
-  description,
-  author: {
-    '@type': author && author.schemaType,
-    name: author && author.name
-  },
-  image: {
-    '@type': 'ImageObject',
-    url: image,
-  },
-  publisher: {
-    '@type': 'Organization',
-    url: organization && organization.url,
-    logo: organization && organization.logo,
-    name: organization && organization.name,
-  },
-  mainEntityOfPage: {
-    '@type': 'WebSite',
-    '@id': site && site.canonicalUrl,
-  },
-  datePublished,
-  dateModified, // Recommended by https://search.google.com/structured-data/testing-tool
-  // Reasoning https://bts.nomadgate.com/medium-evergreen-content
-  // Not only does Google prefer to feature more recent content in its search results, but
-  // users are also more likely to click an article with a recent date listed next to it.
-  // Does it make sense as you can just manipulate the date? Eeeh... Perhaps Google is aware of that.
-})
+const generateBlogPosting = ({
+  url, title, description, image, datePublished, dateModified,
+  tags, site, author, organization } : WebsiteProps & BlogPostProps) => (
+  {
+    '@context': 'http://schema.org',
+    '@type': 'BlogPosting',
+    url,
+    name: title,
+    headline: title,
+    keywords: tags,
+    description,
+    author: {
+      '@type': author && author.schemaType,
+      name: author && author.name
+    },
+    image: {
+      '@type': 'ImageObject',
+      url: image,
+    },
+    publisher: {
+      '@type': 'Organization',
+      url: organization && organization.url,
+      logo: organization && organization.logo,
+      name: organization && organization.name,
+    },
+    mainEntityOfPage: {
+      '@type': 'WebSite',
+      '@id': site && site.canonicalUrl,
+    },
+    datePublished,
+    dateModified, // Recommended by https://search.google.com/structured-data/testing-tool
+    // Reasoning https://bts.nomadgate.com/medium-evergreen-content
+    // Not only does Google prefer to feature more recent content in its search results, but
+    // users are also more likely to click an article with a recent date listed next to it.
+    // Does it make sense as you can just manipulate the date? Eeeh... Perhaps Google is aware of that.
+  })
 
 /**
  * Stringifying eliminates the undefined values, which keeps the JSON-LD somewhat tidy.
- * Some empty objects might remain, but that shouldn't be a problem. 
+ * Some empty objects might remain, but that shouldn't be a problem.
  */
 
 export const createWebsiteJSONLD = (props: WebsiteProps) =>

src/types.ts

@@ -16,7 +16,8 @@ export interface WebsiteProps {
     schemaType: string // 'Person', etc
   }
   site?: {
-    siteName?: string // "If your object is part of a larger web site, the name which should be displayed for the overall site. e.g., "IMDb"."
+    // "If your object is part of a larger web site, the name which should be displayed for the overall site. e.g., "IMDb"."
+    siteName?: string
     canonicalUrl?: string // The index URL of the website (eg https://google.com), used for BlogPosting JSON-LD schema.
   }
 }
@@ -43,7 +44,9 @@ export interface TwitterProps {
 }
 
 export interface BlogPostProps {
-  url?: string // The canonical URL for your page. This should be the undecorated URL, without session variables, user identifying parameters, or counters.
+  // The canonical URL for your page. This should be the undecorated URL, without session
+  // variables, user identifying parameters, or counters.
+  url?: string
   title: string // Title of the post. Max 70 characters.
   description?: string // Should be a short description about the topic, <=200 words. Mainly for SEO purposes.
   image?: string // Based on other SEO tags, an image of 1200x628 with 1.91:1 ratio in PNG, JPEG, or GIF is the optimum.

tslint.json

@@ -9,7 +9,7 @@
     "function-name": false,
     "align": [true, "parameters", "elements", "members", "statements"],
     "import-name": false,
-    "object-shorthand-properties-first": false,
+    "object-shorthand-properties-first": false
   },
   "env": {
     "jest": true