chore: Remove JS Visualisation

[hetunandu]

Description

Remove Visualisation tab fro JS Editor

Summary by CodeRabbit

• Refactor
  • Simplified the response view interface by removing the legacy visualizer tab, streamlining the overall user experience.

[coderabbitai]

Walkthrough

This pull request removes Anvil-related functionality from the JSResponseView.tsx component. The changes consist of deleting imports for getIsAnvilEnabledInCurrentApplication and Visualization as well as eliminating the conditional logic that added the "AI Response Visualizer" tab. The component now builds a simplified response tab structure without any Anvil-specific logic.

Changes

File(s)	Change Summary
app/client/src/components/editorComponents/JSResponseView.tsx	Removed the import for getIsAnvilEnabledInCurrentApplication and Visualization. Deleted the conditional logic that previously added the "AI Response Visualizer" tab based on Anvil.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant E as JSResponseView
    participant T as ResponseTabs

    U->>E: Render editor view
    E->>T: Build default tabs (no conditional Anvil branch)
    T-->>E: Return tab structure
    E->>U: Display response view

Loading

Suggested labels

skip-changelog

Suggested reviewers

• ankitakinger

Poem

In code we prune the extra tree,
Removing branches where Anvil used to be.
Tabs streamlined, with no extra flair,
Clean and simple, light as air.
Happy lines now dance with glee!
🌟🚀

---

📜 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 65e6ab9 and 02f5ff6.

📒 Files selected for processing (1)

• app/client/src/components/editorComponents/JSResponseView.tsx (0 hunks)

💤 Files with no reviewable changes (1)

• app/client/src/components/editorComponents/JSResponseView.tsx

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

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

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.