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

chore: upgrade Typescipt to 5.5.4 #35314

Merged
merged 2 commits into from
Jul 31, 2024
Merged

Conversation

znamenskii-ilia
Copy link
Contributor

@znamenskii-ilia znamenskii-ilia commented Jul 31, 2024

Description

Fixes #35296

Automation

/ok-to-test tags="@tag.All"

🔍 Cypress test results

Tip

🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/10182307436
Commit: 8b0aa1a
Cypress dashboard.
Tags: @tag.All
Spec:


Wed, 31 Jul 2024 15:48:59 UTC

Communication

Should the DevRel and Marketing teams inform users about this change?

  • Yes
  • No

Summary by CodeRabbit

Summary by CodeRabbit

  • New Features

    • Updated TypeScript dependency across multiple modules to support newer features and improvements.
    • Updated colorjs.io dependency in design system packages to enhance functionality.
  • Bug Fixes

    • Enhanced type-checking and overall code quality through dependency updates.
    • Refined color values in both LightModeTheme and DarkModeTheme to improve visual accuracy.
  • Chores

    • Improved flexibility in dependency management by allowing minor and patch updates for TypeScript and colorjs.io.

@znamenskii-ilia znamenskii-ilia requested review from a team and KelvinOm as code owners July 31, 2024 10:52
Copy link
Contributor

coderabbitai bot commented Jul 31, 2024

Walkthrough

The recent updates across the client application's package.json files primarily focused on enhancing the TypeScript dependency by shifting from a fixed version of 5.4 to a more flexible caret version of ^5.5.4. This transition enables the application to incorporate newer features, improvements, and bug fixes from subsequent TypeScript releases, enhancing type-checking capabilities and improving the overall developer experience in various modules.

Changes

Files Change Summary
app/client/package.json Updated TypeScript dependency from "5.4" to "^5.5.4" for improved flexibility and features.
app/client/packages/ast/package.json Updated TypeScript dependency from "5.4" to "^5.5.4" for better compatibility and enhancements.
app/client/packages/dsl/package.json Updated TypeScript dependency from "5.4" to "^5.5.4" to enable newer features and improvements.
app/client/packages/rts/package.json Updated TypeScript dependency from "5.4" to "^5.5.4" for flexibility in version management.
app/client/packages/design-system/widgets/package.json & app/client/packages/storybook/package.json Updated colorjs.io dependency from "^0.4.3" to "^0.5.2" for bug fixes and performance improvements.
app/client/src/plugins/Linting/utils/groupDifferencesByType.ts Enhanced type safety by refining return types using specific types from the deep-diff library.
app/client/packages/design-system/ads/src/Radio/RadioGroup.stories.tsx Removed TypeScript error suppression comments to enforce stricter type checking.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant TypeScript
    participant Application

    Developer->>TypeScript: Update version to ^5.5.4
    TypeScript-->>Application: New features and improvements
    Application->>Developer: Enhanced type-checking and performance
Loading

Assessment against linked issues

Objective Addressed Explanation
Upgrade TypeScript to version 5.5

In summary, the code changes effectively address the objective of upgrading TypeScript to version 5.5, ensuring that the application can leverage improvements and new features that enhance development capabilities.

Poem

In lines of code, a change is made,
TypeScript's version, now upgraded.
From 5.4 to ^5.5.4,
A step to progress, we can explore!
With every patch, our code will shine,
A brighter future, by design! ✨


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:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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
Contributor

@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

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between d780ecb and c326d2c30920f7a55e12576ed71874bef2be451d.

Files ignored due to path filters (1)
  • app/client/yarn.lock is excluded by !**/yarn.lock, !**/*.lock
Files selected for processing (4)
  • app/client/package.json (1 hunks)
  • app/client/packages/ast/package.json (1 hunks)
  • app/client/packages/dsl/package.json (1 hunks)
  • app/client/packages/rts/package.json (1 hunks)
Files skipped from review due to trivial changes (1)
  • app/client/packages/dsl/package.json
Additional comments not posted (3)
app/client/packages/ast/package.json (1)

31-31: Good job! The TypeScript version update is correct.

Updating the TypeScript version to ^5.5.4 allows for minor and patch updates, which helps keep the project up-to-date with the latest features and bug fixes.

app/client/packages/rts/package.json (1)

40-40: Nice work! The TypeScript version update is appropriate.

Updating the TypeScript version to ^5.5.4 allows for minor and patch updates, ensuring the project benefits from the latest improvements and bug fixes.

app/client/package.json (1)

238-238: Well done! The TypeScript version update is correct.

Updating the TypeScript version to ^5.5.4 allows for minor and patch updates, keeping the project current with the latest features and bug fixes.

@znamenskii-ilia znamenskii-ilia requested a review from a team as a code owner July 31, 2024 11:45
@znamenskii-ilia znamenskii-ilia changed the title [Task]: upgrade Typescipt to 5.5.4 chore: upgrade Typescipt to 5.5.4 Jul 31, 2024
@github-actions github-actions bot added skip-changelog Adding this label to a PR prevents it from being listed in the changelog Anvil Pod Issue related to Anvil project Task A simple Todo labels Jul 31, 2024
Copy link
Contributor

@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

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between c326d2c30920f7a55e12576ed71874bef2be451d and 087a3c8.

Files ignored due to path filters (1)
  • app/client/yarn.lock is excluded by !**/yarn.lock, !**/*.lock
Files selected for processing (8)
  • app/client/package.json (1 hunks)
  • app/client/packages/ast/package.json (1 hunks)
  • app/client/packages/design-system/ads/src/Radio/RadioGroup.stories.tsx (1 hunks)
  • app/client/packages/design-system/widgets/package.json (1 hunks)
  • app/client/packages/dsl/package.json (1 hunks)
  • app/client/packages/rts/package.json (1 hunks)
  • app/client/packages/storybook/package.json (1 hunks)
  • app/client/src/plugins/Linting/utils/groupDifferencesByType.ts (1 hunks)
Files skipped from review due to trivial changes (4)
  • app/client/package.json
  • app/client/packages/design-system/widgets/package.json
  • app/client/packages/rts/package.json
  • app/client/packages/storybook/package.json
Files skipped from review as they are similar to previous changes (2)
  • app/client/packages/ast/package.json
  • app/client/packages/dsl/package.json
Additional comments not posted (3)
app/client/src/plugins/Linting/utils/groupDifferencesByType.ts (2)

1-7: Great job importing the necessary types!

The additional imports from the deep-diff library enhance type safety and clarity in the code.


11-13: Excellent update to the return type structure!

Using DiffEdit<unknown, unknown>[], DiffNew<unknown>[], and DiffDeleted<unknown>[] enhances type safety and provides better clarity regarding the nature of the differences being processed.

app/client/packages/design-system/ads/src/Radio/RadioGroup.stories.tsx (1)

Line range hint 44-45:
Great job removing the TypeScript error suppression comments!

This indicates that the underlying type issues have been resolved, enhancing type safety and reducing the potential for runtime errors.

Copy link
Contributor

@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

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 087a3c8 and 94ac93e6ce84e08c5c8668d999d3f6b272837855.

Files selected for processing (1)
  • app/client/packages/design-system/theming/src/color/tests/LightModeTheme.test.ts (28 hunks)
Additional comments not posted (10)
app/client/packages/design-system/theming/src/color/tests/LightModeTheme.test.ts (10)

42-42: Good job updating the expected RGB value!

The updated RGB value for bgAccentHover when lightness is less than 0.06 looks correct. Make sure to verify the correctness of the RGB value in the implementation.


49-49: Nice update on the RGB value!

The updated RGB value for bgAccentHover when lightness is between 0.06 and 0.14 looks accurate. Ensure the RGB value in the implementation matches this expected value.


56-56: Well done updating the RGB value!

The updated RGB value for bgAccentHover when lightness is between 0.14 and 0.21 and hue is between 120 and 300 seems correct. Verify the implementation to ensure it matches this expected value.


63-63: Good update on the RGB value!

The updated RGB value for bgAccentHover when lightness is between 0.14 and 0.21 and hue is not between 120 and 300 looks accurate. Ensure the RGB value in the implementation matches this expected value.


107-107: Great update on the RGB value!

The updated RGB value for bgAccentActive when lightness is less than 0.4 seems correct. Verify the implementation to ensure it matches this expected value.


137-137: Nice work updating the RGB value!

The updated RGB value for bgAccentSubtle when seedLightness is greater than 0.93 looks accurate. Ensure the RGB value in the implementation matches this expected value.


192-192: Good job updating the RGB value!

The updated RGB value for bgNeutral when lightness is greater than 0.85 seems correct. Verify the implementation to ensure it matches this expected value.


367-367: Great update on the RGB value!

The updated RGB value for bgPositive when the seed color is green (hue between 116 and 165) and chroma is greater than 0.11 looks accurate. Ensure the RGB value in the implementation matches this expected value.


435-435: Nice work updating the RGB value!

The updated RGB value for bgNegative when the seed color is red (hue between 5 and 49) and chroma is greater than 0.12 seems correct. Verify the implementation to ensure it matches this expected value.


509-509: Good update on the RGB value!

The updated RGB value for bgWarning when the seed color is yellow (hue between 60 and 115) and chroma is greater than 0.09 looks accurate. Ensure the RGB value in the implementation matches this expected value.

ichik
ichik previously approved these changes Jul 31, 2024
Copy link
Contributor

@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

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 94ac93e6ce84e08c5c8668d999d3f6b272837855 and 8b0aa1a.

Files selected for processing (2)
  • app/client/packages/design-system/theming/src/color/tests/DarkModeTheme.test.ts (18 hunks)
  • app/client/packages/design-system/theming/src/color/tests/LightModeTheme.test.ts (28 hunks)
Files skipped from review as they are similar to previous changes (1)
  • app/client/packages/design-system/theming/src/color/tests/LightModeTheme.test.ts
Additional comments not posted (10)
app/client/packages/design-system/theming/src/color/tests/DarkModeTheme.test.ts (10)

18-18: Verify the correctness of the new expected value for bgAccent.

The expected RGB value for bgAccent has been updated to rgb(0% 20.243% 31.25%). Ensure this change aligns with the intended color logic.


27-27: Verify the correctness of the new expected value for bgAccentHover.

The expected RGB value for bgAccentHover has been updated to rgb(0% 25.612% 37.776%). Ensure this change aligns with the intended color logic.


78-78: Verify the correctness of the new expected value for bgAccentActive.

The expected RGB value for bgAccentActive has been updated to rgb(0% 18.133% 28.462%). Ensure this change aligns with the intended color logic.


108-108: Verify the correctness of the new expected value for bgAccentSubtle.

The expected RGB value for bgAccentSubtle has been updated to rgb(0% 15.035% 24.345%). Ensure this change aligns with the intended color logic.


115-115: Verify the correctness of the new expected value for bgAccentSubtle.

The expected RGB value for bgAccentSubtle has been updated to rgb(0% 10.07% 17.756%). Ensure this change aligns with the intended color logic.


122-122: Verify the correctness of the new expected value for bgAccentSubtle.

The expected RGB value for bgAccentSubtle has been updated to rgb(0% 15.035% 24.348%). Ensure this change aligns with the intended color logic.


467-467: Verify the correctness of the new expected value for bgNegativeSubtleActive.

The expected RGB value for bgNegativeSubtleActive has been updated to rgb(24.04% 0.52339% 2.9937%). Ensure this change aligns with the intended color logic.


479-479: Verify the correctness of the new expected value for bgWarning.

The expected RGB value for bgWarning has been updated to rgb(85.145% 64.66% 8.0285%). Ensure this change aligns with the intended color logic.


484-484: Verify the correctness of the new expected value for bgWarning.

The expected RGB value for bgWarning has been updated to rgb(85.145% 64.66% 8.0285%). Ensure this change aligns with the intended color logic.


489-489: Verify the correctness of the new expected value for bgWarning.

The expected RGB value for bgWarning has been updated to rgb(85.145% 64.66% 8.0285%). Ensure this change aligns with the intended color logic.

@znamenskii-ilia znamenskii-ilia added ok-to-test Required label for CI and removed ok-to-test Required label for CI labels Jul 31, 2024
@znamenskii-ilia znamenskii-ilia merged commit 1dc6944 into release Jul 31, 2024
96 of 97 checks passed
@znamenskii-ilia znamenskii-ilia deleted the chore/upgrade-ts-5_5 branch July 31, 2024 15:49
@coderabbitai coderabbitai bot mentioned this pull request Oct 29, 2024
3 tasks
@coderabbitai coderabbitai bot mentioned this pull request Nov 21, 2024
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Anvil Pod Issue related to Anvil project ok-to-test Required label for CI skip-changelog Adding this label to a PR prevents it from being listed in the changelog Task A simple Todo
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Task]: upgrade Typescript to the last version
3 participants