DisplayDrivers inheriting from DisplayDriver<Tmodel>

[kevinasdzine]

I am experiencing an odd behavior from a display driver for a POCO. I have four POCOs that are used for nested content. The context is a calendar that is presenting data from an external source. The data is imported into the document database via a background task but not as a ContentType. These are my four POCOs

• CompositeEventWeekList
• CompositeEventWeek
• CompositeEventDay
• CompositeEvent

My templates are rendering these out like a desktop calendar (rows of weeks, columns of days)

I have display drivers for each of these to create shapes so that my theme can render them using templates.

The drivers and the templates are almost identical except for the HTML markup needed to lay out the calendar (i.e. weeklist populates an IEnumerable for the weeks, which populates a nested IEnumerable for days, etc.)

the weird thing is that when the day's BuildDisplayAsync method is called, the shape it returns has the day item duplicated (my calendar shows two instances if each day). The other drivers behave correctly.

For illustration, here is my week list's driver

    private async ValueTask PopulateViewModelAsync(CompositeEventWeekList model, CompositeEventWeekListViewModel viewModel, BuildDisplayContext context)
    {
        var tasks = model.CompositeEventsWeeks
            .Select(async item => await _displayManagerCompositeEventsWeek.BuildDisplayAsync(item, context.Updater, "Detail"));
        viewModel.CompositeEventWeeks = await Task.WhenAll(tasks);
    }

and here is the week's driver

    private async ValueTask PopulateViewModelAsync(CompositeEventWeek model, CompositeEventWeekViewModel viewModel, BuildDisplayContext context)
    {
        var tasks = model.CompositeEventDays
            .Select(async item => await _displayManagerCompositeEventsDay.BuildDisplayAsync(item, context.Updater, context.DisplayType));
        viewModel.StartDate = model.StartDate;
        viewModel.EndDate = model.EndDate;
        viewModel.CompositeEventDays = await Task.WhenAll(tasks);
    }

and here is the day's driver

    private async ValueTask PopulateViewModelAsync(CompositeEventDay model, CompositeEventDayViewModel viewModel, BuildDisplayContext context)
    {
        var tasks = model.CompositeEvents
            .Select(async item => await _displayManagerCompositeEvent.BuildDisplayAsync(item, context.Updater, context.DisplayType));
        viewModel.Date = model.Date;
        viewModel.CompositeEvents = await Task.WhenAll(tasks);
    }

The week's driver calls _displayManagerCompositeEventsDay.BuildDisplayAsync and that is the only one that produces duplicate items

Any ideas why that driver might behave differently?

[hishamco]

How is this consumed/called, and is it possible to share a minimal repo with in-memory data, seems something goes wrong during the calling

[kevinasdzine]

The ConmpositeEvents controller returns this for its view. I haven't been able to find good docs on display management for non-contenttype data. Is it possible the template logic is contributing to this?

var compoositeEventWeekList = new CompositeEventWeekList
{
    CompositeEventsWeeks = Enumerable.Range(0, weekCount)
        .Select(i => new CompositeEventWeek
        {
            StartDate = firstWeekday.AddDays(i * 7),
            EndDate = firstWeekday.AddDays(i * 7 + 6),
            CompositeEventDays = calendarEvents
                .Where(item => item.Date >= firstWeekday.AddDays(i * 7) && item.Date <= firstWeekday.AddDays(i * 7 + 6))
                .GroupBy(item => item.Date.Date)
                .OrderBy(group => group.Key)
                .Select(group => new CompositeEventDay
                {
                    Date = group.Key,
                    CompositeEvents = group.OrderBy(item => item.Time).ToList()
                }).ToList()
        }).ToList()
};

return View(new List<IShape> { await _displayManagerCompoositeEventWeekList.BuildDisplayAsync(compoositeEventWeekList, this, "Detail") });

[hishamco]

Can you share a minimal repo with in-memory data, it would be easier to follow with what you did? Or contact me via Discord

[kevinasdzine]

Turns out I had the driver registered to two different places (an alternate test project in the same solution).