From f6dc40cec71547c0d7a08c20d703123946fae73b Mon Sep 17 00:00:00 2001
From: Kha Truong <64438356+khatruong2009@users.noreply.github.com>
Date: Mon, 29 Apr 2024 15:00:49 -0700
Subject: [PATCH] Chore: Removed v0 flutter fragments (#7349)

* chore: remove v0 flutter fragment

* chore: remove move flutter fragment

* chore: remove the move page from the directory and remove move from pages completely
---
 src/directory/directory.mjs                   |  3 ---
 .../graphqlapi/native_common/authz/common.mdx |  4 ---
 .../build-a-backend/storage/move/index.mdx    | 26 -------------------
 3 files changed, 33 deletions(-)
 delete mode 100644 src/pages/[platform]/prev/build-a-backend/storage/move/index.mdx

diff --git a/src/directory/directory.mjs b/src/directory/directory.mjs
index 5ebd48dc3dc..50eb1619f32 100644
--- a/src/directory/directory.mjs
+++ b/src/directory/directory.mjs
@@ -1737,9 +1737,6 @@ export const directory = {
                     {
                       path: 'src/pages/gen1/[platform]/build-ui/formbuilder/lifecycle/index.mdx'
                     },
-                    {
-                      path: 'src/pages/[platform]/prev/build-a-backend/storage/move/index.mdx'
-                    },
                     {
                       path: 'src/pages/gen1/[platform]/build-ui/formbuilder/call-to-action/index.mdx'
                     },
diff --git a/src/fragments/lib-v1/graphqlapi/native_common/authz/common.mdx b/src/fragments/lib-v1/graphqlapi/native_common/authz/common.mdx
index e9b8cba1557..c6e245b3953 100644
--- a/src/fragments/lib-v1/graphqlapi/native_common/authz/common.mdx
+++ b/src/fragments/lib-v1/graphqlapi/native_common/authz/common.mdx
@@ -275,10 +275,6 @@ You can now configure a single GraphQL API to deliver private and public data. P
 
 As discussed in the above linked documentation, certain fields may be protected by different authorization types. This can lead the same query, mutation, or subscription to have different responses based on the authorization sent with the request; Therefore, it is recommended to use the different `friendly_name_<AuthMode>` as the `apiName` parameter in the `Amplify.API` call to reference each authorization type.
 
-import flutter18 from '/src/fragments/lib-v1/graphqlapi/flutter/authz/auth_mode.mdx';
-
-<Fragments fragments={{ flutter: flutter18 }} />
-
 The following snippets highlight the new values in the `amplifyconfiguration.json`/`.dart` and the client code configurations.
 
 The `friendly_name` illustrated here is created from Amplify CLI prompt. There are 4 clients in this configuration that connect to the same API except that they use different `AuthMode`.
diff --git a/src/pages/[platform]/prev/build-a-backend/storage/move/index.mdx b/src/pages/[platform]/prev/build-a-backend/storage/move/index.mdx
deleted file mode 100644
index 3988e173a4c..00000000000
--- a/src/pages/[platform]/prev/build-a-backend/storage/move/index.mdx
+++ /dev/null
@@ -1,26 +0,0 @@
-import { getCustomStaticPath } from '@/utils/getCustomStaticPath';
-                  
-export const meta = {
-  title: 'Move files',
-  description: "Learn more about how to move files using Amplify's storage category.",
-  platforms: ['flutter']
-};
-
-export const getStaticPaths = async () => {
-  return getCustomStaticPath(meta.platforms);
-};
-
-export function getStaticProps(context) {
-  return {
-    props: {
-      platform: context.params.platform,
-      meta
-    }
-  };
-}
-          
-
-
-import flutter0 from '/src/fragments/lib/storage/flutter/move.mdx';
-
-<Fragments fragments={{ flutter: flutter0 }} />