feat: Removing the Beta batch for QBD direct app

[DhaaraniCIT]

Description

feat: Removing the Beta batch for QBD direct app

Clickup

https://app.clickup.com/t/

Summary by CodeRabbit

• New Features

  • Added QuickBooks Desktop (Web Connector) integration option
  • Introduced conditional beta badge for QuickBooks Desktop and Sage 300 CRE integrations

• Bug Fixes

  • Refined visibility of beta status for specific integrations based on organizational settings

[coderabbitai]

Walkthrough

The pull request involves modifications to the integration landing pages for QuickBooks Desktop integrations. Changes include removing the "Beta" badge from the landing-v2 component and adding a new conditional rendering for the "QuickBooks Desktop (Web Connector)" integration in the landing component. The updates also modify the display of the Sage 300 CRE integration badge based on organizational settings.

Changes

File	Change Summary
src/app/integrations/landing-v2/landing-v2.component.html	Removed "Beta" badge for QuickBooks Desktop (Web Connector) integration
src/app/integrations/landing/landing.component.html	Added new conditional rendering for QuickBooks Desktop (Web Connector) integration Modified Sage 300 CRE integration badge display based on organization settings

Poem

🐰 Integrations hop and dance,
Beta badges take their chance,
QuickBooks Desktop finds its way,
Web Connector joins the play,
Sage 300 badge plays hide and seek! 🚀

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2fe9a46 and 1076c1a.

📒 Files selected for processing (2)

• src/app/integrations/landing-v2/landing-v2.component.html (0 hunks)
• src/app/integrations/landing/landing.component.html (0 hunks)

💤 Files with no reviewable changes (2)

• src/app/integrations/landing-v2/landing-v2.component.html
• src/app/integrations/landing/landing.component.html

---

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.

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

[github-actions]

Unit Test Coverage	%	values
Statements	33.02%	( 4131 / 12509 )
Branches	26.37%	( 1173 / 4448 )
Functions	25.59%	( 893 / 3489 )
Lines	33.21%	( 4065 / 12240 )