Internal plugs

[nevo-david]

Summary by CodeRabbit

Release Notes

• New Features

  • Added a new endpoint to retrieve internal plugs for integrations
  • Introduced InternalChannels component to manage and display internal plug configurations
  • Enhanced integration handling with new allIntegrations property across multiple components

• Improvements

  • Added focus management for text editing components
  • Expanded integration context to support more comprehensive data retrieval
  • Improved error handling and data fetching for integration-related functionalities

• Backend Changes

  • Implemented new methods for processing internal plugs
  • Added support for retrieving internal plug metadata for social providers

• Frontend Updates

  • Updated modal components to support broader integration options
  • Introduced new methods for handling integration-specific actions

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
gitroom	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Dec 28, 2024 4:56am
postiz	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Dec 28, 2024 4:56am

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request introduces a comprehensive enhancement to the application's integration and plug management system. The changes span multiple files across backend and frontend components, focusing on adding new methods for retrieving and processing internal plugs. A new InternalChannels component is introduced to render and manage these plugs, and several existing components are updated to support passing and handling of all available integrations.

Changes

File	Change Summary
apps/backend/src/api/routes/integrations.controller.ts	Added getInternalPlugs method to retrieve internal plugs for a given integration
apps/frontend/src/components/launches/*	Updated multiple components to support allIntegrations prop, enhancing integration handling
apps/workers/src/app/plugs.controller.ts	Added internalPlug method to handle internal plug processing
libraries/helpers/src/decorators/post.plug.ts	Introduced new PostPlug decorator for metadata management
libraries/nestjs-libraries/src/integrations/*	Added methods for retrieving and processing internal plugs across integration services

Sequence Diagram

sequenceDiagram
    participant Frontend as Frontend Components
    participant Backend as Integration Controller
    participant Worker as Plugs Worker
    participant Service as Integration Service

    Frontend->>Backend: Request internal plugs
    Backend->>Service: Get internal plugs metadata
    Service-->>Backend: Return internal plugs
    Backend-->>Frontend: Provide internal plugs
    Frontend->>Worker: Trigger internal plug processing
    Worker->>Service: Process internal plug
    Service->>Service: Validate integrations
    Service-->>Worker: Complete processing

Loading

Possibly related PRs

• instagram stories, add collaborators, infrastructure for settings in validation #468: Changes to AddEditModal component involving integration handling

Poem

🐰 Plugs and integrations dance,
A rabbit's code takes a new stance!
Metadata flows with grace and might,
Connecting platforms, pure delight!
Tech magic sprinkled, systems unite! 🚀

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.

---

📜 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 041b076 and 3b27055.

📒 Files selected for processing (18)

• apps/backend/src/api/routes/integrations.controller.ts (3 hunks)
• apps/frontend/src/components/launches/add.edit.model.tsx (3 hunks)
• apps/frontend/src/components/launches/bold.text.tsx (2 hunks)
• apps/frontend/src/components/launches/calendar.tsx (3 hunks)
• apps/frontend/src/components/launches/generator/generator.tsx (1 hunks)
• apps/frontend/src/components/launches/helpers/pick.platform.component.tsx (0 hunks)
• apps/frontend/src/components/launches/helpers/use.integration.ts (1 hunks)
• apps/frontend/src/components/launches/internal.channels.tsx (1 hunks)
• apps/frontend/src/components/launches/providers.options.tsx (2 hunks)
• apps/frontend/src/components/launches/providers/high.order.provider.tsx (5 hunks)
• apps/frontend/src/components/launches/u.text.tsx (2 hunks)
• apps/workers/src/app/plugs.controller.ts (2 hunks)
• apps/workers/src/app/posts.controller.ts (1 hunks)
• libraries/helpers/src/decorators/post.plug.ts (1 hunks)
• libraries/nestjs-libraries/src/database/prisma/integrations/integration.service.ts (2 hunks)
• libraries/nestjs-libraries/src/database/prisma/posts/posts.service.ts (2 hunks)
• libraries/nestjs-libraries/src/integrations/integration.manager.ts (1 hunks)
• libraries/nestjs-libraries/src/integrations/social/x.provider.ts (3 hunks)

---

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.