fix: added fix for vanishing appdetails

[sondermanish]

Description

• modified logic to copy the ApplicationDetails object of the importedApplication to existing application

Fixes #24920

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/9207111058
Commit: 9d426c0
Cypress dashboard url: Click here!

Communication

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

• Yes
• No

[coderabbitai]

Walkthrough

Walkthrough

The changes in ImportExportUtils.java involve restructuring the logic within the setPropertiesToApplicationDetail and setPropertiesToExistingApplication methods to enhance the handling of null checks and property assignments for ApplicationDetail objects.

Changes

File Path	Change Summary
app/server/appsmith-server/src/main/java/com/appsmith/server/helpers/ImportExportUtils.java	- Restructured logic in setPropertiesToApplicationDetail and setPropertiesToExistingApplication. - Simplified null checks and property assignments for ApplicationDetail. - Directly assigned PublishedApplicationDetail and UnpublishedApplicationDetail. - Removed unnecessary conditional checks and method calls.

Assessment against linked issues

Objective	Addressed	Explanation
Ensure that navigation settings changes can be discarded correctly for the first time in a git-connected app (#24920)	✅

---

Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between b3d5055 and 9d426c0.

Files selected for processing (1)

• app/server/appsmith-server/src/main/java/com/appsmith/server/helpers/ImportExportUtils.java (3 hunks)

Files skipped from review as they are similar to previous changes (1)

• app/server/appsmith-server/src/main/java/com/appsmith/server/helpers/ImportExportUtils.java

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

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

CodeRabbit Configration 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.

[coderabbitai]

Actionable comments posted: 1

[NilanshBansal]

/build-deploy-preview skip-tests=true

[github-actions]

Deploying Your Preview: https://github.com/appsmithorg/appsmith/actions/runs/9208065678.
Workflow: On demand build Docker image and deploy preview.
skip-tests: true.
env: ``.
PR: 33698.
recreate: .

[github-actions]

Deploy-Preview-URL: https://ce-33698.dp.appsmith.com

[NilanshBansal]

Approving as couldn't find any test/manual testing failure.
@sondermanish can you pls run all the EE tests as well on a draft EE PR