MudBlazor/MudBlazor

DateOnly support for calendars

Open

#6,178 opened on Jan 18, 2023

View on GitHub
 (17 comments) (18 reactions) (0 assignees)C# (1,631 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (10,394 stars)
PR merge metrics
 (Avg merge 6d 6h) (108 merged PRs in 30d)

Description

Feature request type

Enhance component

Component name

Date Picker

Is your feature request related to a problem?

We love Mud Blazor, but many of us .NET 6/7 users like to use DateOnly for our models that are binded to our form fields. The date pickers do not currently work with DateOnly even when we've specified that we are not interested in time. As a result, we have to write things in automapper which map to our database models. However, doing so seems to make the relationship too difficult for AutoMapper/EF to translate any queries that were written with Linq + ProjectTo. It's causing us to not be able to use the right tools for the right job and accurately reflect our db data types in our domain models.

Describe the solution you'd like

We'd like to be able to use DateOnly for calendars that simply need a date such as a birthday or closing date.

Have you seen this feature anywhere else?

Only in custom implementations

Describe alternatives you've considered

Automapper from a temporary model used only to support mudblazor - the issue with this is that we use ProjectTo to convert queries from our models to our domain db entities, and the mapping becomes too complex to be translated by EF.

Pull Request

  • I would like to do a Pull Request

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributor guide

Research direction
Examine the current DatePicker component implementation for DateTime support and extend it to handle DateOnly by adding a new parameter or converting DateOnly to DateTime internally. Look for existing DateOnly support patterns in MudBlazor or related Blazor libraries.
Tech stack
csharp
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#.NETBlazor
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70