I'm migrating KendoUI for jQuery to React. In jQuery version of Kendo Grid was possible to set "values" property to columns with "id" values.

In React version of the kendo grid, the "values" property for the GridColumn component is not available. How can I make the same like in jQuery version?

Thanks a lot for an each help.

Hello, my team and I are having an issue where kendo is not activated when building with github actions. This issue first surfaced when our license expired which led us to believe it is a caching issue. After updating the license in the variables and clearing the actions cache we are not seeing the activation happen successfully even though the same license jeg activates correctly locally, and says it is correct during the github action build step. I have attached a cut down action .yml for reference. Looking for suggestions on additional things to check.

# This workflow will build a .NET project
# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-net

name: Automated Pipeline

on:
  push:
    branches: [ "master" ]
    paths-ignore:
      - 'docs/**'

env:
    PACKAGE_VERSION: ${{ format('1.0.{0}', github.run_number) }}

jobs:
  build:

    runs-on: windows-latest-l

    steps:
    # Check out code
    - uses: actions/checkout@v4

    # Configure Environment
    - name: Display Package Version
      run: echo "PACKAGE_VERSION = $env:PACKAGE_VERSION"

    - name: Configure .NET
      uses: actions/setup-dotnet@v4
      with:
        dotnet-version: 8.0.x

    - name: Set up Node.js
      uses: actions/setup-node@v4
      with:
        node-version: 20
        cache: "yarn"
        cache-dependency-path: "**/yarn.lock"

    # Restore Dependencies
    - name: Restore dependencies
      run: dotnet restore ./OurApp.sln

    - name: Yarn install Portal
      run: yarn --cwd ./src/WebApp2Frontend install

    - name: Yarn install App
      run: yarn --cwd ./src/WebApp1Frontend install

    - name: Yarn run tests
      run: yarn --cwd ./src/WebApp1Frontend run test

    # Update Version Numbers
    - name: .NET project version updater
      uses: vers-one/dotnet-project-version-updater@v1.6
      with:
          file: "**/*.fsproj"
          version: ${{ env.PACKAGE_VERSION }}

      # Generate code files

      # Activate Kendo Licenses (App)
    - name: Activate Kendo UI License (App)
      run: yarn --cwd ./src/WebApp1Frontend run kendo-ui-license activate
      env:
        KENDO_UI_LICENSE: ${{ secrets.KENDO_UI_LICENSE }}

      # Activate Kendo Licenses (App2)
    - name: Activate Kendo UI License (App2)
      run: yarn --cwd ./src/WebApp2Frontend run kendo-ui-license activate
      env:
        KENDO_UI_LICENSE: ${{ secrets.KENDO_UI_LICENSE }}

    # Build
    - name: Build
      run: dotnet build ./OurApp.sln --no-restore --configuration Release

    # Tests
    - name: Test
      run: dotnet test
      continue-on-error: true

    # Publish
    - name: Publish WebApp2
      run: dotnet publish ./src/WebApp2/WebApp2.fsproj --no-build --configuration Release --output $env:GITHUB_WORKSPACE/artifacts/app2

    - name: Publish WebApp1
      run: dotnet publish ./src/WebApp1/WebApp1.fsproj --no-build --configuration Release --output $env:GITHUB_WORKSPACE/artifacts/app1

    # Upload Artifacts

    # Octopus Deploy Package

    # Data Warehouse and Pulumi package already exists

    # Octopus Deploy Push
  
    # Create Octopus Release

I threw together the easy "patch-package" on latest v8.2.0 below and it worked.

But it seems like the developers must have excluded this value for a reason that i should watch out for?

Or if not, any chance we can get it added officially?

my underlying motivation: I see in all the onItemChange demos the suggested "change item" approach is to iterate the data array via .map() and change the corresponding object item based on matching a unique id property... of course this is a longstanding pattern that honors React's need for immutability, but once lists get large, there's a performance hit that could be avoided by directly targeting the item by index along with other immutability/copying approaches, e.g. toSpliced() is now available in modern browsers.

I have an active license and I could submit bug/feature if this is better requested thru that channel.

diff --git a/node_modules/@progress/kendo-react-grid/Grid.mjs b/node_modules/@progress/kendo-react-grid/Grid.mjs
index ff03785..3f6cb09 100644
--- a/node_modules/@progress/kendo-react-grid/Grid.mjs
+++ b/node_modules/@progress/kendo-react-grid/Grid.mjs
@@ -191,7 +191,8 @@ const z = class z extends r.Component {
           ...this.getArguments(e.syntheticEvent),
           dataItem: e.dataItem,
           field: e.field,
-          value: e.value
+          value: e.value,
+          dataIndex: e.dataIndex
         }
       );
     }, this.onHeaderSelectionChange = (e) => {

I found an example in KendoUI for jQuery here:

https://docs.telerik.com/kendo-ui/knowledge-base/scroll-to-selected-item

How to do it in React TreeView?

Hello.

I have a question. I know, Kendo does not officially support shadow DOM. After all. We were forced to use react grid in the shadow DOM. We have a problem that all pop up windows (paging settings, filter opening) are displayed incorrectly. Without styles and without the possibility to serve the event. Do you have a tip on how to treat it?

• When defining the `GridColumn` properties, such as `cell`, the `className` property doesn't apply as expected. If I remove the cell property from the GridColumn component it works as expected.
• If I don't explicitly define the `headerCell` property, the filter icon (three dots) isn't visible. Hence, I need to manually add the filter options in the header cell.

Note: Everything works as expected when I define each column component individually, without using the `map` function approach.

Please find the attached file with implementation.

I kindly request your help. Thank you.

Im using the Gantt Chart libary for React

so what im trying to do is passing a custom date range props in the GanttWeekView

<GanttWeekView dateRange={calculateWeekDateRange}/>

the problem is whenever you pass custom dateRange props to the view, it will cause the date cell on the right not rerender correctly, for example the initial date is 12th September as shown in the pics below

and i change it to 5th, the date doesnt change as shown below,

for some reason i think whenever the custom dateRange passed, it wont rerender the whole Ganttview component if the date changed, any idea how i can fix this?