Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to tag posts #602

Merged
merged 1 commit into from
Feb 9, 2025
Merged

Option to tag posts #602

merged 1 commit into from
Feb 9, 2025

Conversation

nevo-david
Copy link
Contributor

@nevo-david nevo-david commented Feb 9, 2025

Summary by CodeRabbit

  • New Features

    • Introduced comprehensive tag management so users can add, edit, and assign tags when creating or editing posts.
    • Enhanced the calendar view with dynamic tag indicators and hover details for quick context.
    • Enabled optional title display controls in key sections for a cleaner interface.
  • Style

    • Updated visual styling for tag components to ensure consistent alignment, spacing, and overall design clarity.

Copy link

vercel bot commented Feb 9, 2025

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 Feb 9, 2025 4:04pm
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
postiz ⬜️ Ignored (Inspect) Feb 9, 2025 4:04pm

Copy link

coderabbitai bot commented Feb 9, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request implements comprehensive tag management across the backend and frontend. On the backend, new endpoints and service/repository methods (getTags, createTag, editTag) have been added along with new DTOs and schema models for tags. On the frontend, components have been updated and new ones introduced to manage tag state, display, and styling. Minor adjustments include formatting fixes and an update of the ColorPicker component’s props to enhance external control.

Changes

File(s) Change Summary
apps/backend/src/api/routes/posts.controller.ts
libraries/nestjs-libraries/src/database/prisma/posts/posts.repository.ts
libraries/nestjs-libraries/src/database/prisma/posts/posts.service.ts
libraries/nestjs-libraries/src/dtos/posts/create.post.dto.ts
libraries/nestjs-libraries/src/dtos/posts/create.tag.dto.ts
libraries/nestjs-libraries/src/database/prisma/schema.prisma
Added new endpoints (getTags, createTag, editTag) and associated methods for tag management. Extended post creation/updating to include tags, introduced new DTOs and Prisma models for tags, and updated Organization and Post schemas.
apps/frontend/src/app/global.scss
apps/frontend/src/components/launches/add.edit.model.tsx
apps/frontend/src/components/launches/calendar.context.tsx
apps/frontend/src/components/launches/calendar.tsx
apps/frontend/src/components/launches/helpers/top.title.component.tsx
apps/frontend/src/components/launches/tags.component.tsx
Integrated tag management into the UI. Introduced a new TagsComponent, added tag state to modals, updated calendar item rendering to show tag info, refined TopTitle rendering with a new prop, and applied style fixes (quote normalization & new .tags-top styles).
apps/frontend/src/components/launches/providers/x/x.provider.tsx Removed an unnecessary console.log statement, simplifying the provider’s logic.
libraries/react-shared-libraries/src/form/color.picker.tsx Updated the ColorPicker component by adding optional onChange and value props to allow external control over the color state.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant TC as TagsComponent (UI)
    participant PC as PostsController
    participant PS as PostsService
    participant PR as PostsRepository
    participant DB as Database

    U->>TC: Initiates tag creation (enters tag details)
    TC->>PC: Sends POST /tags with CreateTagDto data
    PC->>PS: Invokes createTag(orgId, body)
    PS->>PR: Calls repository createTag method
    PR->>DB: Inserts new tag record
    DB-->>PR: Returns inserted tag
    PR-->>PS: Returns tag data
    PS-->>PC: Returns tag result
    PC-->>TC: Sends response with new tag
Loading
sequenceDiagram
    participant U as User
    participant AE as AddEditModal (UI)
    participant PC as PostsController
    participant PS as PostsService
    participant PR as PostsRepository
    participant DB as Database

    U->>AE: Fills in post details with tags
    AE->>AE: Updates local tags state
    AE->>PC: Calls schedule() with post data including tags
    PC->>PS: Calls createPost(orgId, CreatePostDto with tags)
    PS->>PR: Invokes createOrUpdatePost with tags
    PR->>DB: Persists post and tag associations
    DB-->>PR: Confirms update
    PR-->>PS: Returns update result
    PS-->>PC: Sends post creation response
    PC-->>AE: Delivers final response
Loading

Possibly related PRs

  • Internal plugs #500: Enhancements in the PostsController for tag management align strongly with these changes.
  • Tag companies on LinkedIn #478: Modifications in the CalendarItem component for displaying tag information relate to the new tag integration.
  • Webhook #591: Introduction of new methods for managing entities in controllers mirrors the tag management updates.

Poem

Hoppity-hop, I code away,
New tags now dance in lines of play.
Endpoints and components, all in sync,
From backend to UI, no detail to shrink.
With every commit, my heart does skip –
A rabbit’s cheer for upgrades—let’s take a hop!
🐇💻 Happy coding, munching on digital carrots!


📜 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 092ea21 and 5b65222.

📒 Files selected for processing (14)
  • apps/backend/src/api/routes/posts.controller.ts (2 hunks)
  • apps/frontend/src/app/global.scss (3 hunks)
  • apps/frontend/src/components/launches/add.edit.model.tsx (5 hunks)
  • apps/frontend/src/components/launches/calendar.context.tsx (2 hunks)
  • apps/frontend/src/components/launches/calendar.tsx (7 hunks)
  • apps/frontend/src/components/launches/helpers/top.title.component.tsx (2 hunks)
  • apps/frontend/src/components/launches/providers/x/x.provider.tsx (0 hunks)
  • apps/frontend/src/components/launches/tags.component.tsx (1 hunks)
  • libraries/nestjs-libraries/src/database/prisma/posts/posts.repository.ts (8 hunks)
  • libraries/nestjs-libraries/src/database/prisma/posts/posts.service.ts (4 hunks)
  • libraries/nestjs-libraries/src/database/prisma/schema.prisma (2 hunks)
  • libraries/nestjs-libraries/src/dtos/posts/create.post.dto.ts (4 hunks)
  • libraries/nestjs-libraries/src/dtos/posts/create.tag.dto.ts (1 hunks)
  • libraries/react-shared-libraries/src/form/color.picker.tsx (2 hunks)
✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

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
🪧 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.

@nevo-david nevo-david merged commit 703f6c7 into main Feb 9, 2025
7 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant