dotnet/aspnetcore

Pass css class in `<ValidationSummary />` to the generated `<ul>`

Chiusa

#43.860 aperta il 9 set 2022

Vedi su GitHubGuida contributor
 (5 commenti) (0 reazioni) (0 assegnatari)C# (10.653 fork)batch import
area-blazorenhancementfeature-blazor-builtin-componentsgood first issuehelp wanted

Metriche repository

Star
 (37.933 stelle)
Metriche merge PR
 (Merge medio 16g 9h) (258 PR mergiate in 30 g)

Descrizione

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

I am trying to pass additional css classes to the generated ul element. I am applying general formatting via the validation-errors css class, but I would like to be able to pass utility classes for spacing (i.e. pt-2 to add 8px of padding to the top of the validation summary).

Describe the solution you'd like

Update <ValidationSummary /> to pass unmatched attributes (via splatting) to the validation-errors element. In the case of class, it should append the passed in classes to the existing validation-errors class.

Additional context

For example:

<ValidationSummary class="pt-2" data-test="validation-errors" />

should result in:

<ul class="validation-errors pt-2"  data-test="validation-errors">
    <!-- Validation Errors -->
</ul>

Guida contributor

Direzione di ricerca
The issue requests adding support for passing CSS classes and other attributes to the `<ul>` element in `<ValidationSummary>`. Examine the current implementation of `ValidationSummary` in the aspnetcore repository, likely in `src/Components/Web/src/Forms/ValidationSummary.cs`. The solution involves using `@attributes` splatting to pass unmatched attributes to the root element, and merging the `class` attribute with the existing `validation errors` class. Check the Blazor documentation for attribute splatting and refer to similar components like `ErrorBoundary` for pattern. Ensure backward compatibility and add tests.
Tech stack
csharp
Dominio
frontend
Tipo issue
Funzionalità
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
Mezza giornata
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
Nuova
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
Abbastanza chiara
Prerequisiti
Basic knowledge of BlazorC# component creation
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
60