Skip to content

Commit

Permalink
reconfig
Browse files Browse the repository at this point in the history
  • Loading branch information
NikolayRn committed May 11, 2023
1 parent 44fe161 commit 394fecd
Show file tree
Hide file tree
Showing 18 changed files with 2,036 additions and 2,115 deletions.
2 changes: 1 addition & 1 deletion .tina/__generated__/_graphql.json

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion .tina/__generated__/_schema.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion .tina/__generated__/client.js

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

45 changes: 1 addition & 44 deletions .tina/__generated__/schema.gql

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

47 changes: 2 additions & 45 deletions .tina/__generated__/types.d.ts

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion .tina/__generated__/types.js

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

7 changes: 2 additions & 5 deletions .tina/config.jsx
Original file line number Diff line number Diff line change
Expand Up @@ -9,10 +9,7 @@ import title from "title";

// Your hosting provider likely exposes this as an environment variable
const branch =
process.env.NEXT_PUBLIC_TINA_BRANCH ||
process.env.NEXT_PUBLIC_VERCEL_GIT_COMMIT_REF ||
process.env.HEAD ||
"main";
"feat/tina-cms";

const WarningIcon = (props) => {
return (
Expand Down Expand Up @@ -79,7 +76,7 @@ const DocsCollection = {
name: "body",
label: "Body",
isBody: true,
templates: [...MDXTemplates],
// templates: [...MDXTemplates],
},
],
};
Expand Down
2 changes: 1 addition & 1 deletion docs/admin-api/admin-api.info.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ Once you have a secured backend account, all the transactions through the Admin

#### Before Getting Started

Before working with Admin API, if you haven't done so, please follow the guide [Getting Started](developers/fuse-sdk/getting-started.mdx).
Before working with Admin API, if you haven't done so, please follow the guide [Getting Started](developers/fuse-sdk/getting-started.md).

> #### 📘For all the Admin APIs you will need to have both your Public and Secret API Keys.
Expand Down
17 changes: 0 additions & 17 deletions docs/developers/deploying-smart-contracts/README.mdx

This file was deleted.

16 changes: 8 additions & 8 deletions docs/developers/fuse-apis/notifications-api.md
Original file line number Diff line number Diff line change
Expand Up @@ -198,19 +198,19 @@ After you have a webhook address (either in your app, or in webhook.site or simi

#### Step 1

Create a webhook with [Create Webhook API](../../notification-api/create-webhook.api.md)
Create a webhook with [Create Webhook API](../../notification-api/create-webhook.api.mdx)

> #### 📘You can find your `projectId` in the URL of your project page
>
> Note that you will need to have an active Fuse account and a project with Public and Secret API keys before getting started. Please refer to [Getting Started](../fuse-sdk/getting-started.md) before the next steps.
#### Step 2

Add addresses to listen to with [Add Webhook Addresses API](../../notification-api/add-webhook-addresses.api.md)
Add addresses to listen to with [Add Webhook Addresses API](../../notification-api/add-webhook-addresses.api.mdx)

> #### 📘
>
> If you don't remember your `webhookId`, you can always fetch all your webhooks with [Get Webhooks for Project](../../notification-api/get-webhooks-for-project.api.md)
> If you don't remember your `webhookId`, you can always fetch all your webhooks with [Get Webhooks for Project](../../notification-api/get-webhooks-for-project.api.mdx)
#### Step 3

Expand All @@ -227,11 +227,11 @@ You can always edit or delete your webhook, add or remove addresses, and change
>
> **Note:** If in any event there is both a wallet address and a token address you subscribed to, you may receive events that may look like duplicates, but you should be able to differentiate between them by looking at the `addressType` field.
* [Delete Webhook](../../notification-api/delete-webhook.api.md)
* [Update Webhook](../../notification-api/update-webhook.api.md)
* [Add Webhook Addresses](../../notification-api/add-webhook-addresses.api.md)
* [Delete Webhook Addresses](../../notification-api/delete-webhook-addresses.api.md)
* [Delete Webhook](../../notification-api/delete-webhook.api.mdx)
* [Update Webhook](../../notification-api/update-webhook.api.mdx)
* [Add Webhook Addresses](../../notification-api/add-webhook-addresses.api.mdx)
* [Delete Webhook Addresses](../../notification-api/delete-webhook-addresses.api.mdx)

You can find all the available endpoints in [Webhooks API Reference](../../notification-api/webhooks.tag.md).
You can find all the available endpoints in [Webhooks API Reference](../../notification-api/webhooks.tag.mdx).


4 changes: 2 additions & 2 deletions docs/developers/fuse-apis/smart-wallets-api.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ sidebar_position: 1
---
# Smart Wallets API

Smart Wallets API provides a Wallets as a Service (WaaS) API for your cross-platform applications. As a developer, you can access the Smart Wallets API via the [fuse-sdk](../fuse-sdk/ "mention") or refer to the [Smart Wallets API reference](../../smart-wallet-api/smart-wallets.tag.md) directly. 
Smart Wallets API provides a Wallets as a Service (WaaS) API for your cross-platform applications. As a developer, you can access the Smart Wallets API via the [fuse-sdk](../fuse-sdk/ "mention") or refer to the [Smart Wallets API reference](../../smart-wallet-api/smart-wallets.tag.mdx) directly. 

Smart Wallets API lets you authenticate users with their Externally Owned Accounts (EOAs) and create Smart Contract wallets, execute gasless transactions through the relay service, fetch balances and tokens, get transaction history, and much more.

Expand All @@ -20,4 +20,4 @@ Before working with Smart Wallets API, if you haven't done so, please follow the
>
> For all Smart Wallets API requests, you will need to add your Public API Key to the request query params under the key `apiKey`.
Once you have your project set and access to your Public API key, you can start working with the Smart Wallets API. Check out the [Smart Wallets API Reference](../../smart-wallet-api/smart-wallets.tag.md) for usage.
Once you have your project set and access to your Public API key, you can start working with the Smart Wallets API. Check out the [Smart Wallets API Reference](../../smart-wallet-api/smart-wallets.tag.mdx) for usage.
2 changes: 1 addition & 1 deletion docs/developers/fuse-apis/trade-api.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,4 +29,4 @@ Before working with Trade API, if you haven't done so, please follow the guide [
>
> For all Trade API requests, you will need to add your Public API Key to the request query params under the key `apiKey`.
Once you have your project set and access to your Public API key, you can start working with the Trade API. Check out the [Trade API Reference](../../trade-api/trade-api.info.md) for usage.
Once you have your project set and access to your Public API key, you can start working with the Trade API. Check out the [Trade API Reference](../../trade-api/trade-api.info.mdx) for usage.

This file was deleted.

2 changes: 1 addition & 1 deletion docs/notification-api/notifications-api.info.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -216,7 +216,7 @@ Create a webhook with [Create Webhook API](./create-webhook.api.mdx)

> #### 📘You can find your `projectId` in the URL of your project page
>
> Note that you will need to have an active Fuse account and a project with Public and Secret API keys before getting started. Please refer to [Getting Started](developers/fuse-sdk/getting-started.mdx) before the next steps.
> Note that you will need to have an active Fuse account and a project with Public and Secret API keys before getting started. Please refer to [Getting Started](developers/fuse-sdk/getting-started.md) before the next steps.
#### Step 2

Expand Down
4 changes: 2 additions & 2 deletions docs/smart-wallet-api/smart-wallets-api.info.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -17,15 +17,15 @@ import Export from "@theme/ApiDemoPanel/Export";

# Smart Wallets API

Smart Wallets API provides a Wallets as a Service (WaaS) API for your cross-platform applications. As a developer, you can access the Smart Wallets API via the [fuse-sdk](developers/fuse-sdk/README.mdx) or refer to the [Smart Wallets API reference](./smart-wallets.tag.mdx) directly. 
Smart Wallets API provides a Wallets as a Service (WaaS) API for your cross-platform applications. As a developer, you can access the Smart Wallets API via the [fuse-sdk](developers/fuse-sdk/README.md) or refer to the [Smart Wallets API reference](./smart-wallets.tag.mdx) directly. 

Smart Wallets API lets you authenticate users with their Externally Owned Accounts (EOAs) and create Smart Contract wallets, execute gasless transactions through the relay service, fetch balances and tokens, get transaction history, and much more.

Each wallet created through the Smart Wallets API is an upgradable Smart Contract wallet deployed on the Fuse network. The wallet is non-custodial. Thus it has an owner in charge of the wallet. The owner controls the wallet funds and can perform other transactions by signing messages and sending them to the relayer.

## Working with Smart Wallets API

Before working with Smart Wallets API, if you haven't done so, please follow the guide [Getting Started](developers/fuse-sdk/getting-started.mdx).
Before working with Smart Wallets API, if you haven't done so, please follow the guide [Getting Started](developers/fuse-sdk/getting-started.md).

#### Ready to start!

Expand Down
Loading

1 comment on commit 394fecd

@vercel
Copy link

@vercel vercel bot commented on 394fecd May 11, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Successfully deployed to the following URLs:

fuse-docs – ./

fuse-docs-fuse-team-v2.vercel.app
fuse-docs-git-feat-tina-cms-fuse-team-v2.vercel.app
docs.fuse.io

Please sign in to comment.