chore: Add null check for PolicyUtils

[abhvsn]

Description

Sorry forgot to add the null check in my previous PR 4c7ce27

/test Sanity

🔍 Cypress test results

Tip

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

---

Mon, 16 Sep 2024 10:11:20 UTC

Communication

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

• Yes
• No

Summary by CodeRabbit

• Bug Fixes
  • Improved error handling in the permissions system by adding a null check for policies, preventing potential crashes.
• Refactor
  • Enhanced the robustness of the permission checking method to ensure stability when handling null inputs.

[coderabbitai]

Walkthrough

The changes in this pull request focus on enhancing the isPermissionPresentInPolicies method within the PolicyUtil class. A null check is introduced for the policies parameter, ensuring that if the set is null, the method will return FALSE immediately. This adjustment prevents potential NullPointerException issues and improves the method's robustness by allowing it to handle cases where the policies input may not be provided.

Changes

File	Change Summary
app/server/appsmith-server/src/main/java/com/appsmith/server/helpers/ce/PolicyUtil.java	Added a null check for the policies parameter in the isPermissionPresentInPolicies method to return FALSE if null.

Possibly related PRs

• fix: NPE while creating a policies copy #36172: Addresses null pointer exceptions related to the policies set in the setUserPermissionsInObject method.
• fix: NPE for policies when policyMap is not present #36323: Modifies the getPolicies() method to return an empty set instead of null, enhancing policy handling robustness.

Suggested labels

Bug, ok-to-test

Poem

In the realm of code, a check was made,
To guard against nulls, a wise upgrade.
Policies now safe, no more despair,
With a simple return, we handle with care.
Robust and steady, our methods now shine,
A brighter future for code, so divine! ✨

---

Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 4c7ce27 and c6d853a.

Files selected for processing (1)

• app/server/appsmith-server/src/main/java/com/appsmith/server/helpers/ce/PolicyUtil.java (1 hunks)

Additional comments not posted (1)

app/server/appsmith-server/src/main/java/com/appsmith/server/helpers/ce/PolicyUtil.java (1)

18-20: Great job adding the null check, class! 👍

This is an excellent example of defensive programming. By checking if the policies set is null and returning FALSE immediately, we prevent potential NullPointerException that could occur when trying to stream a null collection.

This change enhances the robustness of the isPermissionPresentInPolicies method by ensuring it can handle cases where the policies input is not provided, thereby improving error handling and overall stability. Well done!

---

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>, 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 generate interesting stats about this repository and render them as a table.
  -- @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.

[github-actions]

Failed server tests

• com.appsmith.server.fork.ApplicationForkingServiceTests#cloneApplicationForkWithConfigurationTrueWithActionsThrice