Skip to content

Commit e123a4d

Browse files
Merge pull request #1841 from codatio/PEP-1607/decommission-sdk-link
PEP-1607: Remove hosted sdk-link Vercel demo links
2 parents 5afad7c + f8b010f commit e123a4d

4 files changed

Lines changed: 1 addition & 108 deletions

File tree

docs/auth-flow/authorize-embedded-link.md

Lines changed: 0 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -14,29 +14,6 @@ Our Link SDK is a pre-built JavaScript component that neatly sits in your front-
1414

1515
We built it to be flexible so that you can integrate and initialize it in any way you want, and provide the user with a native feel of your authorization journey. As a result, clients using the SDK note that **89%** of their users successfully complete their journeys.
1616

17-
```jsx live
18-
function AuthFlow() {
19-
const onConnection = (connection) =>
20-
alert(`Connection: ${connection.connectionId}`);
21-
const onFinish = () => alert("On finish callback");
22-
23-
const config = {
24-
companyId: "e0e0462f-d7f3-456f-b3e9-0b40afe0245e",
25-
options: {
26-
showLandingPage: true,
27-
},
28-
};
29-
30-
return (
31-
<div>
32-
<p>Click the button below to start authing.</p>
33-
34-
<CodatLink {...config} />
35-
</div>
36-
);
37-
}
38-
```
39-
4017
## Resources
4118

4219
We've provided you with [rich examples on GitHub](https://github.com/codatio/sdk-link/tree/main/examples) that illustrate how you can add the Link component to your project.
@@ -47,12 +24,6 @@ Our user experience team is ready to help you design a high converting and trust
4724

4825
:::
4926

50-
:::info Indicative demo
51-
52-
Curious where Codat's Link flow might fit in your customer's experience? See [our indicative demo](https://sdk-link.vercel.app/).
53-
54-
:::
55-
5627
## Prerequisites
5728

5829
#### Your application

docs/auth-flow/customize/sdk-customize-code.md

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Most of the configuration for the auth flow is currently managed in <a href="htt
1111

1212
However, you can use the SDK's `options` property to override the settings set in the Portal and control them programmatically instead. This is useful if you want more control over the UI based on application-specific logic or want to vary it conditionally.
1313

14-
```jsx live
14+
```js
1515
function AuthFlow() {
1616
const onConnection = (connection) =>
1717
alert(`Connection: ${connection.connectionId}`);
@@ -93,11 +93,6 @@ The `options` prop is optional and accepts an object containing the following op
9393

9494
The object is applied **as the `CodatLink` component is mounted**, so doesn't support hot reloading. Modify the options and refresh the page to see the options reflected.
9595

96-
:::tip Try it out!
97-
98-
Grab our [example file](/documents/example-link-options.json), edit it as desired, and use it in our [Options demo](https://codat-intg-link-sdk-v2-react-18-ui.azurewebsites.net/) to see how the Link UI reflects the changes you make to the properties. You will need a `companyId` to do this.
99-
:::
100-
10196
### Non-modal styling
10297

10398
By default, the Link component is designed to be presented in a modal. To override this, you can use the `nonModal` options setting. When set to `true`, it will:

sidebars/auth-flow.js

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -31,11 +31,6 @@ module.exports = [
3131
label: "NPM",
3232
href: "https://www.npmjs.com/package/@codat/sdk-link-types",
3333
},
34-
{
35-
type: "link",
36-
label: "Try it out",
37-
href: "https://sdk-link.vercel.app/",
38-
},
3934
{
4035
type: "link",
4136
label: "See examples",

static/documents/example-link-options.json

Lines changed: 0 additions & 68 deletions
This file was deleted.

0 commit comments

Comments
 (0)