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: set datasourceId in executeActionDTO during execution #37626

Merged
merged 1 commit into from
Nov 21, 2024

Conversation

nsarupr
Copy link
Contributor

@nsarupr nsarupr commented Nov 21, 2024

Description

Set the correct datasourceId to executeActionDTO when an action is being executed.

Fixes #37627

Automation

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

🔍 Cypress test results

Tip

🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/11948824843
Commit: 458b5c0
Cypress dashboard.
Tags: @tag.Sanity
Spec:


Thu, 21 Nov 2024 08:22:41 UTC

Communication

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

  • Yes
  • No

Summary by CodeRabbit

  • New Features

    • Enhanced functionality to set the correct datasourceId based on the action's context, improving action execution accuracy.
  • Refactor

    • Improved code formatting for clarity without altering existing logic.

@nsarupr nsarupr self-assigned this Nov 21, 2024
Copy link
Contributor

coderabbitai bot commented Nov 21, 2024

Walkthrough

The changes in this pull request modify the populateExecuteActionDTO method in the ActionExecutionSolutionCEImpl class. The primary enhancement is the logic to set the datasourceId in the ExecuteActionDTO based on the viewMode. If viewMode is TRUE, the datasourceId is derived from the publishedAction; otherwise, it comes from the unpublishedAction. Additionally, code formatting improvements were made for better clarity, but no new methods or signatures were introduced.

Changes

Files Change Summary
app/server/appsmith-server/src/main/java/com/appsmith/server/solutions/ce/ActionExecutionSolutionCEImpl.java Modified populateExecuteActionDTO to set datasourceId based on viewMode; improved code formatting.

Assessment against linked issues

Objective Addressed Explanation
Set datasourceId to executeActionDTO when an action is executed (#37627)

Possibly related PRs

Suggested reviewers

  • mohanarpit
  • nidhi-nair
  • sondermanish

🎉 In the code's dance, a new step we see,
With datasourceId, it flows so free!
In viewMode's light, it finds its way,
Clarity shines, come what may!
Let's celebrate this code's fine art,
A leap forward, a brand new start! 🎊


📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 89f9b59 and 458b5c0.

📒 Files selected for processing (1)
  • app/server/appsmith-server/src/main/java/com/appsmith/server/solutions/ce/ActionExecutionSolutionCEImpl.java (1 hunks)
🔇 Additional comments (2)
app/server/appsmith-server/src/main/java/com/appsmith/server/solutions/ce/ActionExecutionSolutionCEImpl.java (2)

255-272: LGTM! The datasourceId assignment logic is correct.

The conditional logic properly sets the datasourceId from either publishedAction or unpublishedAction based on the viewMode, which aligns with the PR objective.


255-272: Consider handling null datasource case.

While the logic is correct, it might be good to add a null check for the datasource object before accessing its ID.

Let's verify if there are cases where datasource could be null:

Consider adding null checks:

 if (TRUE.equals(executeActionDTO.getViewMode())) {
+    if (newAction.getPublishedAction().getDatasource() != null) {
         populatedExecuteActionDTO.setDatasourceId(
                 newAction.getPublishedAction().getDatasource().getId());
+    }
 } else {
+    if (newAction.getUnpublishedAction().getDatasource() != null) {
         populatedExecuteActionDTO.setDatasourceId(
                 newAction.getUnpublishedAction().getDatasource().getId());
+    }
 }

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>, please review it.
    • 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 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 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.

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.

@nsarupr nsarupr requested a review from trishaanand November 21, 2024 07:48
@nsarupr nsarupr added the ok-to-test Required label for CI label Nov 21, 2024
@github-actions github-actions bot added the skip-changelog Adding this label to a PR prevents it from being listed in the changelog label Nov 21, 2024
@github-actions github-actions bot added Anvil Pod Issue related to Anvil project Task A simple Todo labels Nov 21, 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

🧹 Outside diff range and nitpick comments (1)
app/server/appsmith-server/src/main/java/com/appsmith/server/solutions/ce/ActionExecutionSolutionCEImpl.java (1)

255-272: LGTM with a suggestion for defensive programming.

The conditional logic for setting datasourceId based on viewMode is correct. However, consider adding null checks for the datasource object.

Consider this safer implementation:

if (TRUE.equals(executeActionDTO.getViewMode())) {
-    populatedExecuteActionDTO.setDatasourceId(
-            newAction.getPublishedAction().getDatasource().getId());
+    Datasource publishedDatasource = newAction.getPublishedAction().getDatasource();
+    if (publishedDatasource != null) {
+        populatedExecuteActionDTO.setDatasourceId(publishedDatasource.getId());
+    }
} else {
-    populatedExecuteActionDTO.setDatasourceId(
-            newAction.getUnpublishedAction().getDatasource().getId());
+    Datasource unpublishedDatasource = newAction.getUnpublishedAction().getDatasource();
+    if (unpublishedDatasource != null) {
+        populatedExecuteActionDTO.setDatasourceId(unpublishedDatasource.getId());
+    }
}
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 89f9b59 and 458b5c0.

📒 Files selected for processing (1)
  • app/server/appsmith-server/src/main/java/com/appsmith/server/solutions/ce/ActionExecutionSolutionCEImpl.java (1 hunks)

Copy link

Failed server tests

  • com.appsmith.server.refactors.ce.RefactoringServiceCETest#testRefactorActionName_withInvalidName_throwsError

@nsarupr nsarupr merged commit d99789c into release Nov 21, 2024
55 checks passed
@nsarupr nsarupr deleted the chore/set-datasourceId-based-on-viewmode branch November 21, 2024 08:25
github-actions bot pushed a commit to Zeral-Zhang/appsmith that referenced this pull request Nov 27, 2024
…horg#37626)

## Description
> Set the correct datasourceId to executeActionDTO when an action is
being executed.

Fixes appsmithorg#37627

## Automation

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

### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results  -->
> [!TIP]
> 🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/11948824843>
> Commit: 458b5c0
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=11948824843&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.Sanity`
> Spec:
> <hr>Thu, 21 Nov 2024 08:22:41 UTC
<!-- end of auto-generated comment: Cypress test results  -->


## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [x] No


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **New Features**
- Enhanced functionality to set the correct `datasourceId` based on the
action's context, improving action execution accuracy.

- **Refactor**
	- Improved code formatting for clarity without altering existing logic.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Co-authored-by: Nilesh Sarupriya <20905988+nsarupr@users.noreply.github.com>
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]: Set datasourceId to executeActionDTO when an action is executed
2 participants