Create migration guide #79
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for industrial-experience ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
flxlst09
reviewed
Aug 27, 2025
flxlst09
reviewed
Aug 27, 2025
flxlst09
requested changes
Aug 27, 2025
- moved drawer markdowns to legacy - fixed links - added migration guide to sidebar - fixed wrong quotation marks - fixed grammar mistakes
flxlst09
previously approved these changes
Aug 29, 2025
kathrinschalber
commented
Sep 9, 2025
tokyojen
requested changes
Sep 10, 2025
Co-authored-by: tokyojen <[email protected]>
kathrinschalber
changed the title
Standardized the capitalization of 'V4' throughout the migration guide for consistency.
tokyojen
previously approved these changes
Sep 11, 2025
Revised instructions for replacing basic and map navigation elements, recommending use of ix-application and related components. Removed legacy theme section and improved formatting for clarity.
Documented the change in ix-application-header height from 2.75rem (44px) to 3rem (48px) in the 4.0.0 migration guide.
Eliminated a redundant 'components/charts-overview/index' item from the Charts section in the sidebar configuration to prevent duplication.
|
/gemini review |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces a new migration guide and a blog post for the V4.0.0 release. The changes are comprehensive and well-structured. My review focuses on improving the clarity, consistency, and correctness of the new documentation. I've pointed out a few areas for improvement, such as fixing a typo, resolving a 'TBD' placeholder, and standardizing link formats. Additionally, I've identified a duplication issue in the sidebar configuration that should be addressed.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Eliminated repeated 'Drawer' tab items under 'legacy/drawer/index' in the sidebar configuration to avoid redundancy.
flxlst09
previously approved these changes
Oct 1, 2025
There was a problem hiding this comment.
@kathrinschalber Changes approved, I will add another commit on AG Grid migration guide
Added the new UX writing formatting guidelines
nuke-ellington
requested changes
Oct 2, 2025
blog/2025-10-01-release-4/index.md
Outdated
|
|
||
|  | ||
|
|
||
| This release brings full compatibility with Angular 20, helping teams keep their projects aligned with the latest framework improvements. |
There was a problem hiding this comment.
Suggested change
| This release brings full compatibility with Angular 20, helping teams keep their projects aligned with the latest framework improvements. | |
| This release brings full compatibility with Angular 20 and up, helping teams keep their projects aligned with the latest framework improvements. |
docs/home/migration/4_0_0/index.md
Outdated
|
|
||
|  | ||
|
|
||
| <div class="table-full-width table-column-equal-width"> |
There was a problem hiding this comment.
Do you mean our group component? Btw, I've also added the event list, and replaced the big table with a simple bullet list to avoid repetitive content
Refines language in the 2025-10-01 release blog and 4.0.0 migration guide for clarity and accuracy. Updates Angular peer dependency requirements, clarifies AG Grid Figma library changes, and improves instructions for button and elevation variant migrations.
Updated the release notes to specify compatibility with Angular 20 and up, instead of just Angular 20, to better reflect the supported versions.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Jira issue: IX-3140