feat: Expose QBD connector app conditionally

[ashwin1111]

Description

Please add PR description here, add screenshots if needed

Clickup

https://app.clickup.com/

Summary by CodeRabbit

• New Features
  • Introduced support for QuickBooks Desktop integration, including a new direct integration option.
  • Added conditional rendering for integration options based on user permissions and feature availability.
• Bug Fixes
  • Enhanced the display logic for integration options to reflect the availability of direct integration features.
• Chores
  • Updated mock data to include new integration properties.

[coderabbitai]

Warning

Rate limit exceeded

@ashwin1111 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 11 minutes and 44 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 15d7163 and 92264fe.

📒 Files selected for processing (7)

• src/app/branding/expose-app-config.ts (1 hunks)
• src/app/core/models/enum/enum.model.ts (1 hunks)
• src/app/core/models/integrations/integrations.model.ts (1 hunks)
• src/app/core/models/org/org.model.ts (1 hunks)
• src/app/core/services/org/org.fixture.ts (1 hunks)
• src/app/integrations/landing/landing.component.html (1 hunks)
• src/app/integrations/landing/landing.component.ts (1 hunks)

Walkthrough

The changes in this pull request primarily focus on enhancing the integration capabilities for the QuickBooks Direct (QBD_DIRECT) application. This includes updates to configuration constants, the introduction of new enumeration members, modifications to type definitions, and adjustments to the landing component for conditional rendering based on integration availability. Additionally, mock data has been updated to reflect the new integration property. Overall, the changes expand the application's support for the QBD_DIRECT integration.

Changes

File Path	Change Summary
src/app/branding/expose-app-config.ts	Updated QBD_DIRECT property to true for production-1-us environment under fyle.
src/app/core/models/enum/enum.model.ts	Added QBD_DIRECT = 'QuickBooks Connector' to InAppIntegration and QBD_DIRECT = 'QuickBooks Desktop ' to AppName.
src/app/core/models/integrations/integrations.model.ts	Added [InAppIntegration.QBD_DIRECT]: string to InAppIntegrationUrlMap and [AppUrl.QBD_DIRECT]: string to AppUrlMap.
src/app/core/models/org/org.model.ts	Added allow_qbd_direct_integration: boolean to Org type definition.
src/app/core/services/org/org.fixture.ts	Added allow_qbd_direct_integration: true to orgMockData.
src/app/integrations/landing/landing.component.html	Introduced conditional rendering for QBD integration options based on feature availability.
src/app/integrations/landing/landing.component.ts	Added mapping for InAppIntegration.QBD_DIRECT to URL /integrations/qbd_direct.

Possibly related PRs

• feat: Expose QBD Direct Integration #1052: Introduces QBD_DIRECT to the InAppIntegration enum, related to the changes in exposeAppConfig.
• feat: qbd direct pre requisite ts changes #1062: Modifications in QbdDirectOnboardingPreRequisiteComponent, likely interacting with the QBD_DIRECT integration.
• fix: qbd direct export settings onboarding changes and content changes #1082: Onboarding changes for QBD direct settings, relevant to the main PR's updates.
• fix: qbd direct import settings onboarding changes and content changes #1083: Enhancements for onboarding QBD direct import settings, related to the main PR.
• fix: qbd direct advanced settings onboarding changes and content changes #1084: Changes for onboarding QBD direct advanced settings, connected to the main PR.
• feat: Qbd direct je changes #1091: Features related to QBD direct journal entries, relevant to the main PR's updates.
• fix: qbd direct team testing fixes #1095: Testing fixes for the QBD direct team, relevant to the overall integration updates.

Suggested labels

deploy, size/M

Suggested reviewers

• DhaaraniCIT
• ruuushhh

Poem

🐇 In fields of code, we hop and play,
With QBD direct, we pave the way.
New enums and maps, a joyful sight,
Integrations bloom, oh what delight!
So let us cheer, with a twitch of our nose,
For changes made, as our project grows! 🌼

---

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. (Experiment)
• @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	34.06%	( 4196 / 12317 )
Branches	27.64%	( 1202 / 4348 )
Functions	26.69%	( 922 / 3454 )
Lines	34.22%	( 4128 / 12061 )