Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Blazor] Components - loop samples - intro text removal #33675

Merged
merged 1 commit into from
Sep 23, 2024
Merged

[Blazor] Components - loop samples - intro text removal #33675

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions aspnetcore/blazor/components/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1270,8 +1270,6 @@ Consider the following `RenderFragmentChild2` component that has both a componen
When rendering the `RenderFragmentChild2` component in a parent component, use a local index variable (`ct` in the following example) instead of the loop variable (`c`) when assigning the component parameter value and providing the child component's content:

```razor
<h1>Three children with a <code>for</code> loop and an index variable</h1>

@for (int c = 1; c < 4; c++)
{
var ct = c;
Expand All @@ -1285,8 +1283,6 @@ When rendering the `RenderFragmentChild2` component in a parent component, use a
Alternatively, use a [`foreach`](/dotnet/csharp/language-reference/keywords/foreach-in) loop with <xref:System.Linq.Enumerable.Range%2A?displayProperty=nameWithType> instead of a [`for`](/dotnet/csharp/language-reference/keywords/for) loop:

```razor
<h1>Alternative approach without an index variable</h1>

@foreach (var c in Enumerable.Range(1, 3))
{
<RenderFragmentChild2 Id="@($"Child{c}")">
Expand Down
Loading