In Development
Last Updated: 03 Jan 2023 12:31 by ADMIN

Bug report

The TagHelper Grid's TagHelper is not correctly serialized and cannot be used to export hidden columns.

Reproduction of the problem

  • Set the exportable TagHelper for a hidden column to enabled.
<columns>
    <column field="Discontinued" hidden="true">
         <exportable enabled="true" />
    </column>
</columns>			  
  • Open the following REPL example.
  • Export the Grid and observe the exported document.

Current behavior

The Grid TagHelper does not export hidden columns if the exportable TagHelper is enabled identically to the Kendo UI for jQuery Grid column exportable option.

Expected/desired behavior

The Grid TagHelper should be able to export hidden columns if the exportable TagHelper is enabled identically to the Kendo UI for jQuery Grid column exportable option.

Environment

  • Kendo UI version: 2022.3.1109
  • Browser: [all]
In Development
Last Updated: 12 Oct 2022 12:00 by ADMIN
Created by: Stuart
Comments: 0
Category: TreeView
Type: Bug Report
1

### Bug report

The attributes set through the "HtmlAttributes", "ContentHtmlAttributes", and "LinkHtmlAttributes"methods are not applied to the TreeView items.

### Reproduction of the problem

1. Create a TreeView and set attributes by using the "HtmlAttributes", "ContentHtmlAttributes", "LinkHtmlAttributes"methods:

@(Html.Kendo().TreeView()
    .Name("treeview-kendo2")
    .Items(treeview =>
    {
        treeview.Add().Text("My Documents")
        .SpriteCssClasses("k-icon k-i-globe")
        .Expanded(true)
        .Url("/")
        .HtmlAttributes(new { @class = "fairydust1" })
        .ContentHtmlAttributes(new { data_navigate = "navigate_content", @class = "trigger", title = "content_title" })
        .LinkHtmlAttributes(new { data_navigate = "navigate_link", @class = "trigger", title = "content_link" });
    })
)

2. Run the page and inspect the TreeView item.

### Expected/desired behavior

The attributes are serialized and rendered.

### Environment

* **Kendo UI version: 2021.2.616
* **jQuery version: 1.12.4
* **Browser: [all]

In Development
Last Updated: 08 Jun 2021 08:45 by ADMIN
Created by: William
Comments: 3
Category: Grid
Type: Feature Request
17

I'm currently evaluating the ASP .Net Core Components and whilst I'm liking it so far, I have to say - the documentation leaves a lot to be desired.

At the moment, I am trying to use grid and looking at documentation, I have no idea if I am meant to be looking in Kendo.Mvc.UI.Fluent or Kendo.Mvc.UI - and when I am there and find an item, there just isn't enough detail. In addition, the demos section appears to actually be more helpful and I'm constantly looking there.

What caused me to write this is that I have simply enabled GridFilterMode.Row on an instance and whilst I like it, I want to change the default from "Is Equal To" to "Contains"... I have been experimenting for the past few hours without any luck and I'm going round in circles on documentation:

I can see that Filterable requires GridFilterMode, but the documentation is lacking - https://docs.telerik.com/aspnet-core/api/Kendo.Mvc.UI/GridFilterMode#kendomvcuigridfiltermode

I then try to find the filterable modes documentation, but, half the features/methods just don't seem to have any affect whatsoever.

Personally, I'm having great luck learning about your components from the demo section and adapting the code to suite my needs - but, if there isn't a demo, it appears to be a very hard task to learn what is and isn't possible.