docs(IX-3684): update ix to v4 #135

alexkaduk · 2025-11-24T19:18:57Z

No description provided.

netlify · 2025-11-24T19:19:02Z

✅ Deploy Preview for industrial-experience ready!

Name	Link
🔨 Latest commit	`fb27026`
🔍 Latest deploy log	https://app.netlify.com/projects/industrial-experience/deploys/6924afa469136b000868f97b
😎 Deploy Preview	https://deploy-preview-135--industrial-experience.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

gemini-code-assist · 2025-11-24T19:19:36Z

Summary of Changes

Hello @alexkaduk, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on a significant version upgrade for the ix component library within the documentation site. It updates the Docusaurus configuration to reflect version 4, migrates all runtime demo paths and directories from version 3 to version 4, and ensures that the associated example projects have their dependencies aligned with the latest releases. The overall goal is to provide current and accurate documentation and interactive examples for users of the updated ix library.

Highlights

Docusaurus Configuration Update: The playgroundVersion in docusaurus.config.ts has been updated from ^3.0.0 to ^4.0.0, aligning the documentation with the new major version.
Runtime Demo Path Migration: The base URL for runtime demos in src/components/UI/OpenStackblitz/index.tsx has been updated from /runtime/v3 to /runtime/v4, reflecting the new version path for all examples.
Runtime Example Directory Renames: All runtime example directories (Angular, HTML, React, Vue) under static/runtime/v3/ have been renamed to static/runtime/v4/, signifying a complete version upgrade for these interactive examples.
Dependency Updates in Runtime Examples: Various dependencies within the package.json files of the runtime examples have been updated, including ag-grid-angular, ag-grid-community, clsx, echarts-for-react, and @siemens/ix-echarts which is now set to latest.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	`/gemini review`	Performs a code review for the current pull request in its current state.
Pull Request Summary	`/gemini summary`	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	`/gemini help`	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

gemini-code-assist

Code Review

This pull request updates the documentation and runtime examples to support version 4 of Siemens Industrial Experience (iX). The changes include updating the playground version, runtime paths, and dependencies in the example projects. The dependency updates, especially for AG Grid, align with the v4 migration guide. I've noted a potential issue with using latest for the @siemens/ix-echarts package in the example projects, as it could lead to version mismatches. Overall, the changes are consistent and well-aligned with the goal of upgrading to v4.

gemini-code-assist · 2025-11-24T19:21:18Z

static/runtime/v4/angular-standalone/package.json

    "@siemens/ix-angular": "<VERSION>",
    "@siemens/ix-aggrid": "<VERSION>",
-    "@siemens/ix-echarts": "<VERSION>",
+    "@siemens/ix-echarts": "latest",


Using latest for @siemens/ix-echarts could introduce breaking changes if its version becomes incompatible with the other @siemens/ix-* packages, which are pinned to a specific version via the <VERSION> placeholder. To ensure compatibility and prevent unexpected issues in the StackBlitz examples, it would be safer to revert this to <VERSION>, assuming ix-echarts follows the same versioning scheme as the core ix library.

Suggested change

"@siemens/ix-echarts": "latest",

"@siemens/ix-echarts": "<VERSION>",