From 1eac9aed20ba8f2492758d0845fa68e1501a1aa2 Mon Sep 17 00:00:00 2001 From: Demis Bellot Date: Wed, 13 Dec 2023 15:05:47 +0800 Subject: [PATCH] update links --- MyApp/_pages/api-explorer-v1.md | 36 +++++++------- MyApp/_pages/api-explorer.md | 36 +++++++------- MyApp/_pages/autoquery/memory.md | 6 +-- .../commonjs-add-servicestack-reference.md | 2 +- MyApp/_pages/host-configuration.md | 2 +- MyApp/_pages/locode/branding.md | 4 +- MyApp/_pages/locode/code-first.md | 8 ++-- MyApp/_pages/locode/custom-overview.md | 4 +- MyApp/_pages/metadata-page.md | 2 +- MyApp/_pages/releases/v6_00.md | 48 +++++++++---------- MyApp/_pages/releases/v6_07.md | 12 ++--- 11 files changed, 80 insertions(+), 80 deletions(-) diff --git a/MyApp/_pages/api-explorer-v1.md b/MyApp/_pages/api-explorer-v1.md index 6bb2ba421..981e62098 100644 --- a/MyApp/_pages/api-explorer-v1.md +++ b/MyApp/_pages/api-explorer-v1.md @@ -11,7 +11,7 @@ This video provides a quick overview of API Explorer's v1 featureset: ::: info DEMO -A Live demo is available at **/ui** in all ServiceStack **v6+** Apps, e.g: [blazor-wasm-api.jamstacks.net/ui](https://blazor-wasm-api.jamstacks.net/ui) +A Live demo is available at **/ui** in all ServiceStack **v6+** Apps, e.g: [vue-vite-api.jamstacks.net/ui](https://vue-vite-api.jamstacks.net/ui) ::: The entire API Explorer UI is driven by the **rich metadata** around your APIs typed Service Contracts and AppHost's **registered plugins**. @@ -25,7 +25,7 @@ The entire API Explorer UI is driven by the **rich metadata** around your APIs t If your AppHost has the ServiceStack [AuthFeature](/auth/authentication-and-authorization) plugin registered, the home page will display a **Sign In** dialog based on the its **configured Auth Providers**. -This is what you'll see in a new [Blazor WASM](https://blazor-wasm-api.jamstacks.net/ui) project which has **Credentials** Auth, **JWT** as well as **Facebook**, **Google** and **Microsoft** OAuth providers registered in [Configure.Auth.cs](https://github.com/NetCoreTemplates/blazor-wasm/blob/main/MyApp/Configure.Auth.cs) +This is what you'll see in a new [Vue Vite](https://vue-vite-api.jamstacks.net/ui) project which has **Credentials** Auth, **JWT** as well as **Facebook**, **Google** and **Microsoft** OAuth providers registered in [Configure.Auth.cs](https://github.com/NetCoreTemplates/blazor-wasm/blob/main/MyApp/Configure.Auth.cs) ```csharp Plugins.Add(new AuthFeature(() => new CustomUserSession(), @@ -47,7 +47,7 @@ Plugins.Add(new AuthFeature(() => new CustomUserSession(), Where it will dynamically render the **Sign Up** form with the App's enabled Auth capabilities. - + @@ -95,7 +95,7 @@ Plugins.Add(new AdminUsersFeature()); It also displays **Admin UI** links that only **Admin** Users have access to. - + @@ -135,7 +135,7 @@ The `Raw` response forces a `CamelCase` response since the API Explorer interfac Those using `SnakeCase` or `PascalCase` will see a different response outside of API Explorer. ::: - + @@ -176,7 +176,7 @@ public class CreateBooking : ICreateDb, IReturn Generates the following UI:
- +
@@ -188,7 +188,7 @@ to further customize the Input UI control for each property as a **declarative a API Form also supports auto binding [Argument Exceptions](/error-handling) or [Fluent](/validation) & [Declarative](/declarative-validation) Validation rules where any validation errors will be contextually displayed next to the invalid property. Here's both the resulting invalid UI & the Error Response DTO that generated it:
- +
@@ -202,7 +202,7 @@ Another useful API form feature is being able to call APIs with a **JSON request Real-time JSON validation is also displayed for added assistance, warning you whenever the JSON is malformed.
- +
@@ -220,7 +220,7 @@ This is where API consumers would go to learn about each API where it displays a - It's an [AutoQuery CRUD](/autoquery/crud) API implementing `ICreateDb` indicating it creates entries in the **Booking** RDBMS Table - It returns an `IdResponse` which we can intuitively infer returns the new Booking **Id** for successfully created Bookings - + @@ -276,7 +276,7 @@ It includes the necessary steps to call your APIs from client Apps, following th At which point without any code-gen or build tools, they'll end up with an Typed API configured to your APIs endpoint. E.g. this is what it looks like to **Python** developers utilizing our [most recently supported language](/releases/v5_12): - + @@ -325,7 +325,7 @@ public class Booking : AuditBase Where it generates clean API docs displayed in a human-friendly table layout containing properties of its **Request DTO** Type and inherited **base class** properties, starting with the APIs Request DTO followed by all its referenced dependent types - resulting in the details page containing a complete snapshot of all types used in the API: - + @@ -403,7 +403,7 @@ The `*.html` file names aren't important, to create an API doc component it just ### Dynamic Components -[QueryTodos](https://blazor-wasm-api.jamstacks.net/ui/QueryTodos?tab=details) is a more advanced example that generates a dynamic UI shared by all TODO APIs: +[QueryTodos](https://vue-vite-api.jamstacks.net/ui/QueryTodos?tab=details) is a more advanced example that generates a dynamic UI shared by all TODO APIs: ```html