tinacms 0.60.3 → 0.64.0

package/CHANGELOG.md

@@ -1,5 +1,83 @@
 # tinacms
 
+## 0.64.0
+
+### Minor Changes
+
+- 4a3990c7e: Cloudinary media store now serves images over `https` by default. This can now be configured though the handler provided.
+
+  To revert to the old behavior:
+
+  ```ts
+  export default createMediaHandler(
+    {
+      // ...
+    },
+    {
+      useHttps: false,
+    }
+  )
+  ```
+
+  The default for `useHttps` is `true`
+
+## 0.63.0
+
+### Minor Changes
+
+- 3897ec5d9: Replace `branch`, `clientId`, `isLocalClient` props with single `apiURL`. When working locally, this should be `http://localhost:4001/graphql`. For Tina Cloud, use `https://content.tinajs.io/content/<my-client-id>/github/<my-branch>`
+
+  ```tsx
+  // _app.tsx
+  // ...
+  <TinaCMS apiURL={process.env.NEXT_PUBLIC_TINA_API_URL} {...pageProps}>
+    {livePageProps => <Component {...livePageProps} />}
+  </TinaCMS>
+  ```
+
+  DEPRECATION NOTICE: `branch`, `clientId`, `isLocalClient` props will be deprecated in the future
+
+### Patch Changes
+
+- 96e4a77e2: Fixed types
+- b5c22503a: Changes messaging on login page for TinaAdmin when in local-mode
+- Updated dependencies [60f939f34]
+  - @tinacms/toolkit@0.56.6
+
+## 0.62.0
+
+### Minor Changes
+
+- 70da62fe8: deprecated the use of `getStaticPropsForTina`
+
+### Patch Changes
+
+- 0afa75df1: 2342 - [TinaAdmin] Truncates the `filename` column for the Document List View
+- 7dafce89d: Fixed issue where content creator was invalid
+- 3de8c6165: Enabled branch creation in branch switcher
+- fee183f8f: add "switch to default branch" recover option to error boundary
+- 5c070a83f: feat: Add UI banner for when in localMode
+- Updated dependencies [ddf81a4fd]
+- Updated dependencies [20260a82d]
+- Updated dependencies [0370147fb]
+- Updated dependencies [3de8c6165]
+- Updated dependencies [2eaad97bf]
+- Updated dependencies [5c070a83f]
+  - @tinacms/toolkit@0.56.5
+
+## 0.61.1
+
+### Patch Changes
+
+- Updated dependencies [2c7718636]
+  - @tinacms/toolkit@0.56.4
+
+## 0.61.0
+
+### Minor Changes
+
+- 229feda1d: add .nvmrc file for setting preferred node version
+
 ## 0.60.3
 
 ### Patch Changes

package/README.md

@@ -1,289 +1,4 @@
-> Heads up - if you haven't already done so, read through the [CLI documentation](https://tina.io/docs/tina-cloud/cli/) to make sure you have a GraphQL server running locally.
+# TinaCMS
+> The Fastest Way to Edit Next.js Content
 
-For a real-world example of how this is being used checkout the [Tina Cloud Starter](https://github.com/tinacms/tina-cloud-starter).
-
-## Getting started
-
-Npm:
-
-```bash
-npm install --save-dev tinacms
-```
-
-Yarn:
-
-```bash
-yarn add --dev tinacms
-```
-
-## The TinaCMS API Client
-
-This package exports a class which acts as [TinaCMS external API](https://tina.io/docs/apis/) for the Tina Content API. This is a headless GraphQL API that's serverd via Tina Cloud or locally from within the Tina CLI.
-
-```ts
-import { Client, LocalClient } from "tinacms";
-const client = new Client({
-  organizationId: "the ID you get from Tina Cloud",
-  clientId: "the client ID you get from Tina Cloud",
-  branch: "main",
-  tokenStorage: "LOCAL_STORAGE" | "MEMORY" | "CUSTOM",
-});
-
-// For a simpler setup while working locally you can instantiate the LocalClient as a convenience
-const client = new LocalClient();
-```
-
-The `Client` does a few things:
-
-- Manages auth with Tina Cloud
-- Provides a `request` function for working with the GraphQL API
-
-Start by initializing the `LocalClient` - which automatically connects with your locally-running GraphQL server. From there, you can make GraphQL requests:
-
-### `client.request`
-
-```ts
-const client = new LocalClient();
-
-await client.request(
-  (gql) => gql`#graphql
-query BlogPostQuery($relativePath: String!) {
-  {
-    getPostsDocument(relativePath: "") {
-      data {
-        title
-      }
-    }
-  }
-}
-`,
-  { variables: { relativePath: "hello-world.md" } }
-);
-```
-
-> This API currently doesn't support filtering and sorting "list" queries. We have plans to tackle that in upcoming cycles.
-
-## `useGraphQLForms`
-
-While GraphQL is a great tool, using it with Tina can be difficult. GraphQL can query across multiple nodes, but since each document would require its own Tina form it could be difficult to sync the data with your query with all of the forms you'd need to build. The Tina GraphQL server knows all about your content schema so we're actually able to build forms automatically by inspecting your query. To see this in action, pass your query into the `useGraphqlForms` hook:
-
-```tsx
-import { useGraphqlForms } from 'tinacms'
-
-const query = gql => gql`#graphql
-  query BlogPostQuery($relativePath: String!) {
-    {
-      getPostsDocument(relativePath: $relativePath) {
-        data {
-          title
-        }
-      }
-    }
-  }
-`
-
-const MyPage = (props) => {
-  const [payload, isLoading] = useGraphqlForms<PostQueryResponseType>({
-    query,
-    variables: { relativePath: `${props.filename}.md` },
-  });
-
-  isLoading ? <div>Loading...</div> : <MyComponent {...payload}>
-}
-```
-
-If Tina is enabled you can see a form for the `getPostsDocument` request. If you query for multiple documents, you should see multiple forms:
-
-```tsx
-const query = (gql) => gql`#graphql
-  query BlogPostQuery($relativePath: String!) {
-    {
-      # this generates a Tina Form
-      getSiteNavsDocument(relativePath: "site-nav.md") {
-        data {
-          items {
-            title
-            link
-          }
-        }
-      }
-      # this generates a separate Tina Form
-      getPostsDocument(relativePath: $relativePath) {
-        data {
-          title
-        }
-      }
-    }
-  }
-`;
-```
-
-### Formify
-
-If you'd like to control the output of those forms, tap into the `formify` callback:
-
-##### Form customization:
-
-```tsx
-import { useGraphqlForms } from "tinacms";
-import { useCMS } from "tinacms";
-
-const [payload, isLoading] = useGraphqlForms({
-  query,
-  formify: ({ formConfig, createForm, createGlobalForm, skip }) => {
-    if (formConfig.id === "getSiteNavsDocument") {
-      return createGlobalForm(formConfig);
-    }
-
-    return createForm(formConfig);
-  },
-  variables: { relativePath: `${props.filename}.md` },
-});
-
-// or to skip the nav from creating a form altogether:
-const [payload, isLoading] = useGraphqlForms({
-  query,
-  formify: ({ formConfig, createForm, skip }) => {
-    if (formConfig.id === "getSiteNavsDocument") {
-      return skip();
-    }
-
-    return createForm(formConfig);
-  },
-  variables: { relativePath: `${props.filename}.md` },
-});
-```
-
-##### Field customization:
-
-Since your forms are built automatically, `formify` can also be used to customize fields:
-
-```tsx
-const [payload, isLoading] = useGraphqlForms({
-  query,
-  formify: ({ formConfig, createForm, skip }) => {
-    return createForm({
-      ...formConfig,
-      fields: formConfig.fields.map((field) => {
-        if (field.name === "title") {
-          // replace `text` with `textarea`
-          field.component = "textarea";
-        }
-        return field;
-      }),
-    });
-  },
-  variables: { relativePath: `${props.filename}.md` },
-});
-```
-
-## `useDocumentCreatorPlugin`
-
-This hook allows your editors to safely create new pages. Note that you'll be responsible for redirecting the user after a new document has been created. To use this:
-
-```tsx
-import { useDocumentCreatorPlugin } from "tinacms";
-
-// args is of type:
-// {
-//   collection: {
-//     slug: string;
-//   };
-//   relativePath: string;
-//   breadcrumbs: string[];
-//   path: string;
-// }
-useDocumentCreatorPlugin((args) => window.location.assign(buildMyRouter(args)));
-```
-
-### Customizing the content creator options
-
-To prevent editors from creating documents from certain collections, provide a filter function:
-
-```tsx
-// options are of type:
-// {
-//   label: string;
-//   value: string;
-// }[]
-useDocumentCreatorPlugin(null, (options) =>
-  options.filter((option) => option.name !== "post")
-);
-```
-
-## Authentication with Tina Cloud
-
-While this package comes with low-level APIs for authentication with Tina Cloud, the easiest way to get started is to use the `TinaCloudAuthWall` component, which prevents children from rendering until a valid session has been established with Tina Cloud.
-
-### `TinaCloudAuthWall`
-
-```tsx
-import { TinaCloudAuthWall, Client } from "tinacms";
-
-const TinaWrapper = ({ children }) => {
-  const cms = React.useMemo(() => {
-    return new TinaCMS({
-      apis: {
-        tina: new Client({
-          // config
-        })
-      },
-      ...
-    });
-  }, []);
-
-  return <TinaCloudAuthWall cms={cms}>{children}</TinaCloudAuthWall>;
-};
-```
-
-Props for TinaCloudAuthWall
-
-| Prop                         | Description                                                                                                                                                                                                                                                                                            |
-| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `cms`                        | An instance of a [CMS](http://localhost:3000/docs/cms/#cms-configuration)                                                                                                                                                                                                                              |
-| `getModalActions` (optional) | A function that returns a list of actions / buttons that will be rendered to the model. Each button has name, action, and can be primary or not. The name is the text that will be displayed. The action is a function that will be run when the button is clicked. See example below for more details |
-
-```tsx
-return (
-  <TinaCloudAuthWall
-    cms={cms}
-    getModalActions={({ closeModal }) => {
-      return [
-        {
-          action: async () => {
-            //  use your own state to get in and out of edit mode
-            closeModal();
-          },
-          name: "close",
-          primary: false,
-        },
-      ];
-    }}
-  >
-    <Component {...pageProps} />
-  </TinaCloudAuthWall>
-);
-```
-
-> Note: when using the LocalClient, TinaCloudAuthWall won't display a login screen, there is no authentication for the local GraphQL server.
-
-### Authenticating without TinaCloudAuthWall
-
-You can also authenticate with the `Client` directly:
-
-```ts
-const client = new Client({
-  // config
-});
-
-const EditSiteButton = () => {
-  const cms = useCMS();
-  const onClick = async () => {
-    await client.authenticate().then((token) => {
-      cms.enable();
-    });
-  };
-
-  return <button onClick={onClick}>Edit This Site</button>;
-};
-```
+[Checkout the docs](https://tina.io/docs/setup-overview/) for information on how to get started

package/dist/client/index.d.ts

@@ -42,6 +42,7 @@ export declare class Client {
     private options;
     events: EventBus;
     constructor({ tokenStorage, ...options }: ServerOptions);
+    get isLocalMode(): boolean;
     setBranch(branchName: string): void;
     addPendingContent: (props: any) => Promise<unknown>;
     getSchema: () => Promise<GraphQLSchema>;