Merge pull request linode#100 from linode/release-1.1.1

Release 1.1.1

Author: nmelehan

src/content/changelog/4-7-0-2019-10-07.md

@@ -0,0 +1,35 @@
+---
+title: '4.7.0: 2019-10-21'
+date: 2019-10-21T12:00:00.000Z
+version: 4.7.0
+changelog:
+  - API
+---
+### Added
+
+* Added the `tfa_enabled` property to the [/account/users](/api/v4/account-users) endpoint collection. This property returns a boolean value indicating if the User has Two Factor Authentication (TFA) enabled. See the Create Two Factor Secret ([POST /profile/tfa-enable](https://developers.linode.com/api/v4/profile-tfa-enable#post)) endpoint to enable TFA.
+* Added the `upgrade` property to the Initiate Pending Host Migration/DC Migration ([POST /linode/instances/{linodeId}/migrate](https://developers.linode.com/api/v4/linode-instances-linode-id-migrate/#post)) endpoint
+* The `secondary_entity` property of a `disk_delete` Event will now be populated with the disk that has been deleted. This property was not previously assigned a value. The primary `entity` property for a `disk_delete` Event is associated with the Linode that the disk was deleted from.
+  * Refer to the List Events ([GET /account/events](https://developers.linode.com/api/v4/account-events)) and View Event ([GET /account/events/{eventId}](https://developers.linode.com/api/v4/account-events-event-id)) endpoints to review your Events.
+
+### Changed
+
+* Changed how Notifications for promotional credits are generated:
+  * For expiring promotional credits, a Notification was only generated when the promotion was within 7 days of expiring _and_ when 90% of the credit had been used. This Notification would be of type `promotion`.
+  * Now, two different Notifications are generated:
+    * A Notification of type `promo_expiration` will be generated when the promotion is within 7 days of its expiration date.
+    * A Notification of type `promo_credit_limit` will be generated when 90% or more of the promotion's credit has been used.
+  * Notifications of type `promotion` will no longer be generated.
+  * Refer to the List Notifications ([GET /account/notifications](https://developers.linode.com/api/v4/account-notifications)) endpoint to view your account's notifications.  Refer to the `active_promotions` property in the response from the View Account ([GET /account](https://developers.linode.com/api/v4/account)) endpoint for details of your current promotions.
+
+### Fixed
+
+* Improved the error response messages of the Initiate Pending Host Migration/DC Migration ([POST /linode/instances/{linodeId}/migrate](https://developers.linode.com/api/v4/linode-instances-linode-id-migrate/#post)) endpoint:
+  * This endpoint will return an error when called when both of these conditions are true: 
+    * The Linode has a /116 IPv6 pool, or IP Sharing is enabled.
+    * An NGN data center was specified for the `region` property.
+  * Previously, the error message returned when a /116 pool caused the migration to fail would state that IP Sharing was enabled, which may not have been the case.
+  * The endpoint will now return a different error message when a /116 IPv6 pool is present.
+* Support Tickets returned by the List Support Tickets ([GET /support/tickets](https://developers.linode.com/api/v4/support-tickets)) endpoint can now be sorted by the `closed`, `opened`, and `updated` properties of a Ticket. This was the intended behavior, but specifying a sorting was not previously honored in the response.
+* In rare circumstances, a Linode may exist without an Invoice Item that corresponds to it. If the Initiate Pending Host Migration/DC Migration ([POST /linode/instances/{linodeId}/migrate](https://developers.linode.com/api/v4/linode-instances-linode-id-migrate/#post)) endpoint was called on a Linode under these circumstances, the endpoint would return an error. This error will no longer appear, and the migration will proceed normally (or fail for any other reasons listed in the endpoint's documentation).
+* The Import Domain ([POST /domains/import](https://developers.linode.com/api/v4/domains-import/#post)) endpoint would sometimes return a 400 error code when a server error had occurred. A 500 error code will now be returned instead, which is in line with our API's [guidance on error codes](https://developers.linode.com/api/v4/#errors).

src/css/components/0_utilities/typography.css

@@ -22,15 +22,6 @@ input[type="text"] {
   @apply p-4 mt-2 mb-2 bg-ThemeBeige block;
 }
 
-.api-body pre code {
-  @apply p-2 mt-2 mb-4 bg-ThemeBeige block;
-  overflow-x: auto;
-}
-
-.api-body code {
-  @apply p-1 bg-ThemeBeige;
-}
-
 .api-desc code {
   @apply font-normal px-1 bg-ThemeTagGrey inline text-xs relative;
   padding-top: 4px;

src/pages/api/v4.js

@@ -2,6 +2,8 @@ import React from "react";
 // import PropTypes from "prop-types";
 import { graphql, StaticQuery } from "gatsby";
 import Markdown from "react-markdown/with-html";
+import { Prism as SyntaxHighlighter } from "react-syntax-highlighter";
+import { atomDark } from "react-syntax-highlighter/dist/esm/styles/prism";
 
 import Layout from "../../components/4_layouts/layout";
 import SEO from "../../components/0_utilities/seo";
@@ -27,6 +29,25 @@ const HeadingRenderer = props => {
   return <Heading {...props} />;
 };
 
+class CodeBlock extends React.PureComponent {
+  render() {
+    const { value } = this.props;
+
+    return (
+      <SyntaxHighlighter
+        language="shell"
+        style={atomDark}
+        className="api-samples"
+        codeTagProps={{
+          style: { whiteSpace: "pre-wrap" }
+        }}
+      >
+        {value}
+      </SyntaxHighlighter>
+    );
+  }
+}
+
 class APIDocs extends React.Component {
   componentDidMount() {
     window.addEventListener("scroll", () => {
@@ -58,7 +79,7 @@ class APIDocs extends React.Component {
               <Markdown
                 source={n.info.description}
                 escapeHtml={false}
-                renderers={{ heading: HeadingRenderer }}
+                renderers={{ heading: HeadingRenderer, code: CodeBlock }}
                 className="md:mt-8 api-body"
               />
             </div>