Browse Source

refactor: Remove unnecessary Blazor web app configuration from localization examples

pull/25174/head
maliming 6 months ago
parent
commit
7d2686d065
No known key found for this signature in database GPG Key ID: A646B9CB645ECEA4
  1. 5
      docs/en/Community-Articles/2026-03-29-Url-Based-Localization/POST.md
  2. 10
      docs/en/framework/fundamentals/url-based-localization.md

5
docs/en/Community-Articles/2026-03-29-Url-Based-Localization/POST.md

@ -143,11 +143,6 @@ Normal page-to-page navigation (within the same language) remains client-side an
### Example module configuration
```csharp
PreConfigure<AbpAspNetCoreComponentsWebOptions>(options =>
{
options.IsBlazorWebApp = true;
});
Configure<AbpRequestLocalizationOptions>(options =>
{
options.UseRouteBasedCulture = true;

10
docs/en/framework/fundamentals/url-based-localization.md

@ -143,11 +143,6 @@ Blazor Server uses SignalR (WebSocket) for the interactive circuit. The HTTP mid
### Example module configuration
````csharp
PreConfigure<AbpAspNetCoreComponentsWebOptions>(options =>
{
options.IsBlazorWebApp = true;
});
Configure<AbpRequestLocalizationOptions>(options =>
{
options.UseRouteBasedCulture = true;
@ -188,11 +183,6 @@ Same as Blazor Server — you must manually add `@page "/{culture}/..."` routes
````csharp
// Server project
PreConfigure<AbpAspNetCoreComponentsWebOptions>(options =>
{
options.IsBlazorWebApp = true;
});
Configure<AbpRequestLocalizationOptions>(options =>
{
options.UseRouteBasedCulture = true;

Loading…
Cancel
Save