Scheduler new Titleformat and titleformatter example

Radzen.Blazor Components
1

please can you provide an example for using the new:
RadzenScheduler view titles - new TitleFormat and TitleFormatter parameters on the scheduler views give full control over each view's title: a format string, or a formatter function for complete customization.

2

TitleFormat is a standard composite format string - {0} is the first date and {1} is the last date displayed by the view:

<RadzenScheduler @ref=@scheduler TItem="Appointment" Data=@appointments
                 StartProperty="Start" EndProperty="End" TextProperty="Text">
    <RadzenDayView TitleFormat="{0:dddd, MMMM d yyyy}" />
    <RadzenWeekView TitleFormat="Week: {0:MMM d} - {1:MMM d, yyyy}" />
    <RadzenMonthView TitleFormat="{0:MMMM yyyy}" />
</RadzenScheduler>

For anything that needs logic (week numbers, custom culture handling, etc.) use TitleFormatter instead - it receives the first and last date and returns the title:

<RadzenWeekView TitleFormatter=@FormatWeekTitle />

string FormatWeekTitle(DateTime start, DateTime end)
{
    var week = System.Globalization.ISOWeek.GetWeekOfYear(start);
    return $"Week {week} ({start:MMM d} - {end:MMM d, yyyy})";
}

TitleFormatter takes precedence if both are set. The dates passed are the actual range shown by the view - e.g. the month view passes the first and last day of the month, the year views pass the start and end of the displayed year (respecting StartMonth).

TitleFormat strings are formatted with the scheduler Culture, so {0:MMMM yyyy} localizes automatically.

3

Thank you for the explanation, however in the playground, the formatweektitle is producing the following error:
The type or namespace name 'ISOWeek' does not exist in the namespace 'System.Globalization' (are you missing an assembly reference?) The best overload for 'AppendFormatted' does not have a parameter named 'format' The best overload for 'AppendFormatted' does not have a parameter named 'format'

while in VS it runs smoothly.

4

To keep the size of our playground we use assembly trimming and that’s why such errors might occur - feel free to use my example in your app instead.