docs: Fix typo
This commit is contained in:
vatsashah45
Родитель
f7f816056e
Коммит
59e0976ebc
|
|
@ -5,7 +5,7 @@ uid: Uno.Extensions.Authentication.HowToAuthentication
|
|||
|
||||
`Uno.Extensions.Authentication` provides you with a consistent way to add authentication to your application. It is recommended to use one of the built-in `IAuthenticationService` implementations. This tutorial will use the custom authorization to validate user credentials.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ Using **cookies** is a common way to store tokens that are needed to authenticat
|
|||
> [!IMPORTANT]
|
||||
> To follow these steps, you first need to have an authentication system set up. We recommend choosing one of the `IAuthenticationProvider` implementations provided by Uno Extensions. Cookie authorization can complement any of the tutorials such as [Get Started with Authentication](xref:Uno.Extensions.Authentication.HowToAuthentication).
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
### 1. Enable cookies
|
||||
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ uid: Uno.Extensions.Authentication.HowToMsalAuthentication
|
|||
|
||||
`MsalAuthenticationProvider` allows your users to sign in using their Microsoft identities. It wraps the [MSAL library](https://github.com/AzureAD/microsoft-authentication-library-for-dotnet) from Microsoft into an implementation of `IAuthenticationProvider`. This tutorial will use MSAL authorization to validate user credentials.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ uid: Uno.Extensions.Authentication.HowToOidcAuthentication
|
|||
|
||||
`OidcAuthenticationProvider` allows your users to sign in using their identities from a participating identity provider. It can wrap support for any [OpenID Connect](https://openid.net/connect/) backend, such as [IdentityServer](https://duendesoftware.com/products/identityserver) into an implementation of `IAuthenticationProvider`. This tutorial will use the OIDC authorization to validate user credentials.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ uid: Uno.Extensions.Authentication.HowToWebAuthentication
|
|||
|
||||
`WebAuthenticationProvider` provides an implementation that displays a web view in order for the user to login. After login, the web view redirects back to the application, along with any tokens. This tutorial will use web authorization to validate user credentials.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ uid: Uno.Extensions.Configuration.HowToConfiguration
|
|||
|
||||
`Uno.Extensions.Configuration` provides you with a consistent way to view configuration data from a number of distinct sources. It leverages the `IOptions<T>` interface from [Microsoft.Extensions.Options](https://learn.microsoft.com/dotnet/api/microsoft.extensions.options) to offer [read-only](https://learn.microsoft.com/dotnet/core/extensions/configuration#concepts-and-abstractions) access to values organized into sections. Unlike the [Writable Configuration](xref:Uno.Extensions.Configuration.HowToWritableConfiguration) (aka Settings) pattern, this does not allow for programmatic writing by itself.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ A special interface called `IWritableOptions<T>` is registered as a service when
|
|||
> [!NOTE]
|
||||
> It is common to see this referred to as the _settings_ pattern in certain documentation. This is because the `IOptions<T>` interface is often used to represent settings that can be changed by the user.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
### 1. Prepare for writing configuration values
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ This tutorial will walk you through how to set up this feature and use it to man
|
|||
> [!WARNING]
|
||||
> This approach to resolving dependencies is _not_ recommended, and should serve primarily as a stopgap measure while you refactor your codebase to use constructor injection.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ uid: Uno.Extensions.DependencyInjection.HowToDependencyInjection
|
|||
|
||||
Dependency Injection (DI) is an important design pattern when building loosely-coupled software that allows for maintainability and testing. This tutorial will walk you through how to register services so that they can be consumed throughout your application.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ uid: Uno.Extensions.Hosting.HowToHostingSetup
|
|||
> [!WARNING]
|
||||
> The steps outlined here are unnecessary if you used the new project wizard template to create your solution. Otherwise, it is recommended that you follow the [Creating an application with Uno.Extensions article](xref:Uno.Extensions.HowToGettingStarted) for creating an application from the template.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
### 1. Installation
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ It's often necessary to include an API key alongside requests to a web API. This
|
|||
|
||||
* Knowledge of how to [register an endpoint for HTTP requests](xref:Uno.Extensions.Http.HowToHttp)
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ uid: Uno.Extensions.Http.HowToHttp
|
|||
|
||||
When working with a complex application, centralized registration of your API endpoints is a good practice. This allows you to easily change the endpoint for a given service, and to easily add new services.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ uid: Uno.Extensions.Http.HowToRefit
|
|||
|
||||
When accessing resources with a [REST-style](https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm) API is a significant part of your application, it is common to look for an SDK that provides a strongly-typed client for the API. This allows you to avoid writing boilerplate code to make requests and deserialize responses. There is sometimes no SDK available yet for the API you want to use, or it's not compatible with your target platform. With the design goal of avoiding boilerplate code in mind, we will walk through how to use [Refit](https://github.com/reactiveui/refit) to quickly create a strongly-typed client for a REST API and register it with the service collection as an endpoint.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ uid: Uno.Extensions.Localization.HowToUseLocalization
|
|||
|
||||
`Uno.Extensions.Localization` uses the locale-specific resources from `resw` files placed in folders corresponding to the well-known language tag (eg en-US). By opting into localization, an implementation of `IStringLocalizer` is registered with your application's `IServiceCollection`.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ uid: Uno.Extensions.Logging.UseInternalLogging
|
|||
|
||||
`Uno.Extensions.Logging` provides logging capabilities tailored to your target platform. It allows the recording of events for XAML layout, Uno-internal messages, and custom events with severity and verbosity levels of your choice.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes your application has already opted into logging. To find out how to do this, refer to the tutorial [here](xref:Uno.Extensions.Logging.UseLogging)
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ uid: Uno.Extensions.Logging.UseLogging
|
|||
|
||||
`Uno.Extensions.Logging` allows you to leverage logging capabilities tailored to your target platform to easily record events for XAML layout, Uno-internal messages, and custom events with severity and verbosity levels of your choice.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ Using backward/forward navigation in your app requires a degree of extra conside
|
|||
> [!NOTE]
|
||||
> This guide uses predefined code created by the Uno Template using the `Recommended` preset, however, it uses the `MVVM` approach for the examples instead of `MVUX` defined in the `Recommended` preset.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [Creating an application with Uno.Extensions article](xref:Uno.Extensions.HowToGettingStarted) for creating an application from the template.
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ It makes sense to allow `TabBar` to be the dominant navigation surface on these
|
|||
|
||||
This tutorial will show you how to build a responsive layout with multiple navigation controls such as `NavigationView` and the [Uno Toolkit](https://github.com/unoplatform/uno.toolkit.ui) `TabBar` which use the _same_ navigation service behind the scenes.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ uid: Uno.Extensions.Navigation.Advanced.ContentControl
|
|||
|
||||
If you want to display a view in a specific location in a page, `ContentControl` is the ideal UI element. For example, you might want to display a view in a `Grid` or `StackPanel` in a specific location. You can use a `ContentControl` to display a view in a specific location.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ Choosing the right control for your navigation needs is important, and one commo
|
|||
> [!NOTE]
|
||||
> This guide uses predefined code created by the Uno Template using the `Recommended` preset, however, it uses the `MVVM` approach for the examples instead of `MVUX` defined in the `Recommended` preset.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ uid: Uno.Extensions.Navigation.Advanced.Panel
|
|||
|
||||
Sometimes your application may need to switch between multiple views without the overhead of controls like `Frame` which support a navigation stack. In this case, it makes sense to define sectors of potential view content as **regions** and use another control to toggle the `Visibility` of the multiple views directly. This tutorial will show you how to use a `Panel` to switch between views.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ var builder = this.CreateBuilder(args)
|
|||
> [!NOTE]
|
||||
> This guide uses predefined code created by the Uno Template using the `Recommended` preset, however, it uses the `MVVM` approach for the examples instead of `MVUX` defined in the `Recommended` preset.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [Creating an application with Uno.Extensions article](xref:Uno.Extensions.HowToGettingStarted) for creating an application from the template.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ Routes provide an easy and dynamic way of navigating through your app, either vi
|
|||
|
||||
This topic walks through the process of defining routes.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [Creating an application with Uno.Extensions article](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ This topic walks through how to use Navigation to display the details of an item
|
|||
> [!NOTE]
|
||||
> This guide uses predefined code created by the Uno Template using the `Recommended` preset, however, it uses the `MVVM` approach for the examples instead of `MVUX` defined in the `Recommended` preset.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ This topic walks through using Navigation to display a prompt using a `MessageDi
|
|||
> [!NOTE]
|
||||
> This guide uses predefined code created by the Uno Template using the `Recommended` preset, however, it uses the `MVVM` approach for the examples instead of `MVUX` defined in the `Recommended` preset.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ This topic covers using Navigation to navigate between two pages using frame-bas
|
|||
> [!NOTE]
|
||||
> This guide uses predefined code created by the Uno Template using the `Recommended` preset, however, it uses the `MVVM` approach for the examples instead of `MVUX` defined in the `Recommended` preset.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ This topic walks through controlling Navigation from code, either in the code-be
|
|||
> [!NOTE]
|
||||
> This guide uses predefined code created by the Uno Template using the `Recommended` preset, however, it uses the `MVVM` approach for the examples instead of `MVUX` defined in the `Recommended` preset.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ This topic walks through controlling Navigation from XAML. This includes specify
|
|||
> [!NOTE]
|
||||
> This guide uses predefined code created by the Uno Template using the `Recommended` preset, however, it uses the `MVVM` approach for the examples instead of `MVUX` defined in the `Recommended` preset.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ This topic walks through using Navigation to request a value from the user. For
|
|||
> [!NOTE]
|
||||
> This guide uses predefined code created by the Uno Template using the `Recommended` preset, however, it uses the `MVVM` approach for the examples instead of `MVUX` defined in the `Recommended` preset.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ uid: Uno.Extensions.Navigation.HowToShowDialog
|
|||
|
||||
This topic provides a step-by-step guide on using Navigation to display a Dialog.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ uid: Uno.Extensions.Serialization.HowToSerialization
|
|||
|
||||
Accessing the serialized and deserialized representation of an object can be important for dynamic, data-rich applications. Uno.Extensions supports the [new serialization technique](https://devblogs.microsoft.com/dotnet/try-the-new-system-text-json-source-generator) powered by code generation, but you can optionally revert to the previous one which uses reflection.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [**Creating an application with Uno.Extensions** documentation](xref:Uno.Extensions.HowToGettingStarted) to create an application from the template.
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ uid: Uno.Extensions.Storage.HowToRequiredEntitlements
|
|||
|
||||
On Apple platforms (iOS, Mac Catalyst) the Uno storage extension uses the OS Key Chain service to store secrets. This requires your application to have the [`keychain-access-groups`](https://developer.apple.com/documentation/bundleresources/entitlements/keychain-access-groups) entitlement to work properly.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This guide assumes you used the template wizard or `dotnet new unoapp` to create your solution. If not, it is recommended that you follow the [instructions](xref:Uno.Extensions.HowToGettingStarted) for creating an application from the template.
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ uid: Uno.Extensions.ThemeService.Overview
|
|||
|
||||
This topic explains how to use the `ThemeService` for runtime theme switching and persisting user theme preferences.
|
||||
|
||||
## Step-by-steps
|
||||
## Step-by-step
|
||||
|
||||
1. **Register ThemeService**:
|
||||
Add the `ThemeService` to your project's host builder configuration.
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче