No Records template not visible for Grid TagHelper with Local Data Binding

[kendo-bot]

Current behavior

Using the following configuration the No Records message is not shown:

<kendo-grid mobile="Disabled" name="Grid" loader-type="GridLoaderType.Skeleton">
 <columns>
 <column field="ProductName" title="Product Name">
 </column>
 <column field="UnitPrice" format="{0:C}" title="Unit Price" width="130">
 </column>
 <column field="UnitsInStock" title="Units In Stock" width="130">
 </column>
 <column field="Discontinued" title="Discontinued" width="130">
 </column>
 </columns>
 <datasource type="DataSourceTagHelperType.Ajax" page-size="20" server-operation="false" data="@Model">
 </datasource>
 <filterable enabled="true">
 </filterable>
 <scrollable enabled="true" />
 <pageable enabled="true">
 </pageable>
 <sortable enabled="true" />
<no-records template="string HTML template, automatically centered" />
</kendo-grid>

Expected behavior

The No Records message should be visible.

[alestoya]

The issue seems to stem from the lack of a schema and, more in particular, a model rather than an issue particularly related to the empty template.

Internal jQuery manipulations are being performed for the AJAX DataSource under the hood, which are specifically tailored for the kendo.data.transports['aspnetmvc-ajax'] transport type.

The following REPL verifies this supposition - https://netcorerepl.telerik.com/QJagGUlg314xomCr49

Although there is a fix candidate, I am not fully certain whether this behavior might fall within the expected category. Considering the fact that we also strongly advocate for clients to define a schema for more complex responses.

In contrast to the Grid HTML Helper, the TagHelper counterpart does not have a direct association with the underlying model within the data configuration. Instead, the options are purely serialized as they are annotated.

Where the HTML Helper internally serializes a schema based on the passed type and directly associated ModelMetaDataProvider:

I believe shaking hands on how to tackle this would be beneficial. Thus, I am plugging @aleksandarevangelatov for a second opinion on the matter.