fix: action creator zendesk actions not shown fixed

[sneha122]

Description

This Pr fixes two issues:

1. Action creator was not showing external saas actions
2. The error received from CS was not clearly visible in response tab

Fixes #Issue Number
or
Fixes #38899

Warning

If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation

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

🔍 Cypress test results

Tip

🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/13046482198
Commit: 53f6abc
Cypress dashboard.
Tags: @tag.Datasource
Spec:

---

Thu, 30 Jan 2025 06:41:29 UTC

Communication

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

• Yes
• No

Summary by CodeRabbit

Summary by CodeRabbit

• Bug Fixes
  • Improved error handling for different plugin types (DB, SAAS, EXTERNAL_SAAS)
  • Updated API action filtering logic to include EXTERNAL_SAAS plugin type and now includes AI plugin type as well

[coderabbitai]

Walkthrough

The pull request introduces modifications to error handling and action filtering logic across two TypeScript files. The changes primarily focus on expanding the support for different plugin types, specifically EXTERNAL_SAAS, in error response processing and API action filtering. The modifications aim to enhance the flexibility of handling various plugin types within the application's action management system.

Changes

File	Change Summary
app/client/.../getErrorFromActionResponse.ts	Updated getErrorMessageFromActionResponse to return body for DB, SAAS, and EXTERNAL_SAAS plugin types
app/client/.../helpers.tsx	Modified getApiAndQueryOptions to filter API actions, including EXTERNAL_SAAS and removing exclusion of AI plugin type

Possibly related PRs

• fix: external saas redirection when api created and navigated #38518: The changes in this PR involve adding support for the PluginType.EXTERNAL_SAAS, which is directly related to the modifications made in the main PR that expanded the error handling for multiple plugin types, including EXTERNAL_SAAS.
• fix: Plugin Action Editor navigation issue with git #37670: This PR also deals with the handling of action IDs in the context of plugin actions, which aligns with the main PR's focus on enhancing error handling for different plugin types, including SAAS and EXTERNAL_SAAS.
• fix: conditionally set FqN name for partial import #37694: The changes in this PR involve conditional logic based on the plugin type, which is relevant to the main PR's updates to the error handling logic for various plugin types, including SAAS and EXTERNAL_SAAS.

Suggested Labels

Integrations Product, Integrations Pod General, Query & JS Pod

Suggested Reviewers

• hetunandu
• ayushpahwa

Poem

🚀 Code flows like a river wild,
Plugin types dancing, unreconciled,
Error messages finding their way,
Flexibility blooms on this coding day,
Refactoring magic, smooth and bright! 🌟

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f2ec0cc and 53f6abc.

📒 Files selected for processing (1)

• app/client/src/components/editorComponents/ActionCreator/helpers.tsx (1 hunks)

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

• app/client/src/components/editorComponents/ActionCreator/helpers.tsx

⏰ Context from checks skipped due to timeout of 90000ms (8)

• GitHub Check: perform-test / rts-build / build
• GitHub Check: perform-test / client-build / client-build
• GitHub Check: perform-test / server-build / server-unit-tests
• GitHub Check: client-unit-tests / client-unit-tests
• GitHub Check: client-prettier / prettier-check
• GitHub Check: client-lint / client-lint
• GitHub Check: client-check-cyclic-deps / check-cyclic-dependencies
• GitHub Check: client-build / client-build

---

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 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. (Beta)
• @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.