Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JNG-6168 bump deps for missing translations #524

Merged

Conversation

noherczeg
Copy link
Contributor

No description provided.

Copy link

coderabbitai bot commented Mar 4, 2025

Walkthrough

The changes update dependency versions in two configuration files of the UI React project. In the dependency fragment file, versions for several MUI packages (data grid, date pickers, tree view, and license) have been bumped from 7.23.6 to newer releases (7.27.2, 7.27.1, and 7.26.0) with a condition for the license update. In the pnpm-lock file, similar updates are applied to both standard and pro versions of MUI packages along with an update to internal dependencies and the addition of a new dependency, [email protected].

Changes

File Change Summary
.../actor/package.json.dependencies.fragment.hbs Updated dependency versions for MUI packages: @mui/x-data-grid{{ getMUIDataGridPlanSuffix }} (7.23.6 → 7.27.2), @mui/x-date-pickers{{ getMUIPickersPlanSuffix }} (7.23.6 → 7.27.1), @mui/x-tree-view (7.23.6 → 7.26.0), and @mui/x-license (7.23.6 → 7.26.0, conditional).
.../actor/pnpm-lock.pro.yaml Updated MUI packages: @mui/x-data-grid-pro (7.23.6 → 7.27.2), @mui/x-date-pickers-pro (7.23.6 → 7.27.1), @mui/x-license (7.23.6 → 7.26.0), @mui/x-tree-view (7.23.6 → 7.26.0), @mui/x-data-grid (7.23.6 → 7.27.2), @mui/x-internals (7.23.6 → 7.26.0), @mui/x-date-pickers (7.23.6 → 7.27.1); added [email protected].

Poem

I hop through lines of code so neat,
Upgrading packages on nimble feet.
Carrots of versions, fresh and bright,
MUI updates make my day light.
Hoppy leaps in code—a bunny’s delight! 🐇


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (3)
judo-ui-react/src/main/resources/actor/package.json.dependencies.fragment.hbs (1)

10-11: Consider synchronizing version numbers for better maintainability.

I notice that the various MUI X components are now using slightly different version numbers (7.27.2 for data-grid, 7.27.1 for date-pickers). While this may be intentional to target specific fixes, consider whether aligning these versions would simplify future maintenance.

judo-ui-react/src/main/resources/actor/pnpm-lock.pro.yaml (2)

39-49: Updated MUI X Dependencies in Importers

The dependency versions for several MUI X packages have been updated in the importers block:

  • @mui/x-data-grid-pro now uses specifier 7.27.2
  • @mui/x-date-pickers-pro now uses specifier 7.27.1
  • @mui/x-license now uses specifier 7.26.0
  • @mui/x-tree-view now uses specifier 7.26.0

Please verify that these bumps are consistent with your package dependency fragment (e.g. in your package.json template) and that any breaking changes introduced by the updated versions have been addressed in the UI.


1831-1835: Addition of New Dependency: [email protected]

A new dependency use-sync-external-store has been added at version 1.4.0, with the appropriate peer dependency on React (^16.8.0 || ^17.0.0 || ^18.0.0 || ^19.0.0). Please ensure that this addition is intentional, that it integrates correctly within your project code, and that any new usage is covered by tests or documentation updates.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2faa02e and 8ea83a8.

⛔ Files ignored due to path filters (1)
  • judo-ui-react/src/main/resources/actor/pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (2)
  • judo-ui-react/src/main/resources/actor/package.json.dependencies.fragment.hbs (1 hunks)
  • judo-ui-react/src/main/resources/actor/pnpm-lock.pro.yaml (12 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: ⏳ Build, test and deploy artifacts
🔇 Additional comments (4)
judo-ui-react/src/main/resources/actor/package.json.dependencies.fragment.hbs (3)

10-13:

❓ Verification inconclusive

Check dependency tree for potential conflicts.

When updating packages to newer versions, it's important to verify that there are no conflicts with other dependencies. The lock file update mentioned in the summary should handle this, but it's worth confirming that the application builds and runs correctly with these new versions.


🏁 Script executed:

#!/bin/bash
# Determine if there's a package.json file in the same directory to check
find judo-ui-react/src/main/resources/actor -name "package.json" -type f

Length of output: 72


Dependency Tree Verification – Manual Review Required

The updated dependency fragment appears correct. However, our automated search didn’t locate a package.json file in the judo-ui-react/src/main/resources/actor directory, so we couldn’t automatically verify that the lock file update prevents conflicts. Please manually confirm that the application builds and runs as expected, ensuring there are no dependency conflicts when using the updated versions.

  • File under review: judo-ui-react/src/main/resources/actor/package.json.dependencies.fragment.hbs
  • Snippet:
    "@mui/x-data-grid{{ getMUIDataGridPlanSuffix }}": "7.27.2",
    "@mui/x-date-pickers{{ getMUIPickersPlanSuffix }}": "7.27.1",
    "@mui/x-tree-view": "7.26.0",
    {{# if isMUILicensed }}"@mui/x-license": "7.26.0",{{/ if }}

Please verify the dependency tree and build/run processes manually to ensure compatibility with the new versions.


13-13:

❓ Verification inconclusive

Verify the conditional license dependency.

The MUI X license dependency is conditionally included based on isMUILicensed flag. Ensure this flag is correctly set in your build environment, as it's crucial for proper license validation in production.


🏁 Script executed:

#!/bin/bash
# Look for where isMUILicensed is defined or set in the codebase
rg -A 2 -B 2 "isMUILicensed" --glob "!*.lock*" --glob "!*node_modules*"

Length of output: 4025


Verify MUI License Configuration
The conditional inclusion of the "@mui/x-license" dependency in the package.json fragment is based on the isMUILicensed flag. Our search confirms that this flag is referenced consistently across the codebase—in both the Handlebars template and within the TSX and Java files (e.g., in ReactStoredVariableHelper.java and vite-env.d.ts.hbs). Please ensure that:

  • The build environment correctly sets the MUI license configuration (e.g., via the VITE_MUI_LICENSE_KEY in your environment and the logic in getMUILicensePlan()).
  • All conditional inclusion points (in package.json.dependencies.fragment.hbs and src/main.tsx.hbs) operate as intended in production to validate the license properly.

10-13:

❓ Verification inconclusive

Dependency version updates look appropriate.

The MUI X components have been updated to newer versions which should address the missing translations issue mentioned in the PR title. The version increments are relatively minor (from 7.23.6 to versions between 7.26.0 and 7.27.2) and should be backward compatible.


🌐 Web query:

What are the changes between MUI X version 7.23.6 and 7.27.2?

💡 Result:

Between MUI X versions 7.23.6 and 7.27.2, several improvements, bug fixes, and minor breaking changes were introduced across Data Grid, Date Pickers, and Charts components. Here are the key updates:

Data Grid Changes

  • Excel Export Enhancements: Improved serialization performance and fixed Web Worker demo issues in development mode [7][10].
  • New Props: Added resetPageOnSortFilter to reset pagination after sorting/filtering [7].
  • Pagination Fixes: Addressed unexpected behavior when using "-1" for "All" rows and ensured consistent server-side data navigation [7][9].
  • TypeScript Changes:
    • GridSortModel became a readonly array (breaking change for direct mutations) [7][9].
    • rowCount in pagination no longer accepts undefined [7].
  • Rendering & Behavior:
    • Fixed renderContext calculation with scroll bounce [7].
    • Improved header filter keyboard navigation and toolbar button onClick order [7].
  • Localization: Added Bangla (bn-BD) and improved Hungarian (hu-HU), Russian (ru-RU), Polish (pl-PL), and Ukrainian (uk-UA) locales [7][10].

Date and Time Pickers

  • Mobile Fixes: Corrected currentMonthCalendarPosition behavior and vertical alignment in multi-input Date Range Pickers [7].

Charts

  • Pie Chart Fix: Resolved empty series array handling [7].
  • Line Chart: Enabled default animations (disablable via skipAnimation) [4].

Breaking Changes

  • Type Safety: GridSortModel now uses a readonly array type, requiring updates to mutation logic [9].
  • Webpack 5 Requirement: Dropped Webpack 4 support due to native browser feature usage (e.g., Optional Chaining) [4].

Performance & Stability

  • Mount/Resize Optimizations: Reduced Data Grid rendering latency [7].
  • State Management: Refactored row state propagation for consistency [7].

Other

  • Core Dependencies: Updated @mui/material peer dependency to ^5.15.14 for Charts [4].

For migration, run codemods (npx @mui/x-codemod@latest v7.0.0/preset-safe) and review type changes in GridSortModel[1][7][9].

Citations:


Verified MUI X Dependency Update – Minor API Adjustments Not Impacting This File

The updates in the dependency fragment are consistent with the migration path from v7.23.6 to the current versions. As confirmed by the release notes, the new versions for @mui/x-data-grid (7.27.2), @mui/x-date-pickers (7.27.1), and @mui/x-tree-view (7.26.0) introduce several bug fixes, enhancements, and some minor API changes (for example, GridSortModel is now a readonly array). These changes primarily address issues like the missing translations noted in the PR title and should not affect usage within this file, provided any required codemods for breaking changes are applied.

  • File: judo-ui-react/src/main/resources/actor/package.json.dependencies.fragment.hbs (Lines 10-13)

Overall, the dependency updates are appropriate and align with our migration goals.

judo-ui-react/src/main/resources/actor/pnpm-lock.pro.yaml (1)

857-2659: Comprehensive Bump of MUI‐Related Packages in the Lockfile

Across the lockfile’s deeper sections (in the packages and snapshots sections), several entries for MUI-related packages have been updated:

  • @mui/x-data-grid-pro and @mui/x-data-grid are now pinned to version 7.27.2
  • @mui/x-date-pickers-pro and @mui/x-date-pickers are updated to version 7.27.1
  • @mui/x-internals is bumped to 7.26.0
  • @mui/x-license and @mui/x-tree-view have been revised to 7.26.0

These changes ensure consistency between the upgrade in your dependency fragment and the lockfile. Please run your full test suite to confirm that the updated versions work seamlessly with your codebase and that peer dependency constraints (especially on React) remain satisfied.

@noherczeg noherczeg merged commit 7abf715 into develop Mar 4, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants