Added prop to table

[maximgorbatyuk]

Summary by CodeRabbit

• New Features

  • Added a new column "Последнее сообщение" to the Telegram subscription table, displaying the timestamp of the last message sent.
  • Introduced a button to manually send updates for each Telegram subscription, with a success alert upon completion.

• Bug Fixes

  • Corrected the table header structure to ensure all headers are properly grouped in a single row.

[coderabbitai]

Walkthrough

A new optional field, lastMessageSent, was added to the StatDataCacheChangeSubscription interface. The admin table displaying these subscriptions was updated to include a new column for this field. A new method was introduced in both the component and service to allow sending updates via a POST request.

Changes

File(s)	Change Summary
src/app/models/telegram.ts	Added lastMessageSent: Date | null to StatDataCacheChangeSubscription interface.
src/app/modules/admin/components/telegram/stat-data-change-subscriptions/stat-data-cache-records.component.html	Corrected table header structure; added "Последнее сообщение" column for lastMessageSent.
src/app/modules/admin/components/telegram/stat-data-change-subscriptions/stat-data-cache-records.component.ts	Added sendUpdates method to trigger sending updates for a subscription.
src/app/services/telegram-subscriptions.service.ts	Added sendUpdates(id: string): Observable<void> method to perform POST request to send updates endpoint.

Sequence Diagram(s)

sequenceDiagram
    participant AdminUser
    participant StatDataCacheRecordsComponent
    participant TelegramSubscriptionsService
    participant Server

    AdminUser->>StatDataCacheRecordsComponent: Click "Send Updates" on a subscription
    StatDataCacheRecordsComponent->>TelegramSubscriptionsService: sendUpdates(item.id)
    TelegramSubscriptionsService->>Server: POST /api/telegram-subscriptions/{id}/send-updates
    Server-->>TelegramSubscriptionsService: 200 OK
    TelegramSubscriptionsService-->>StatDataCacheRecordsComponent: Observable completes
    StatDataCacheRecordsComponent-->>AdminUser: Show success alert "Сообщение отправлено"

Loading

Poem

A new field appears, a date to display,
"Последнее сообщение" now leads the way.
With a click, updates fly,
And success alerts reply.
The table is tidy, the service is spry—
Hopping forward, code rabbits never shy!
🐇✨

Tip

⚡️ Faster reviews with caching

• CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

---

📜 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 6443e39 and 3232353.

📒 Files selected for processing (1)

• src/app/modules/admin/components/telegram/stat-data-change-subscriptions/stat-data-cache-records.component.html (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• src/app/modules/admin/components/telegram/stat-data-change-subscriptions/stat-data-cache-records.component.html

---

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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @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.

[coderabbitai]

Actionable comments posted: 1

🔭 Outside diff range comments (1)

src/app/modules/admin/components/telegram/stat-data-change-subscriptions/stat-data-cache-records.component.html (1)

90-95: 🛠️ Refactor suggestion

Add "Send Updates" action to the dropdown menu.

The component has a sendUpdates method, but there's no UI element in the dropdown menu to trigger it.

Add a new action item to the dropdown menu:

  <li>
    <a class="dropdown-item" (click)="getOpenAiReport(item)"
      >Open AI данные</a
    >
  </li>
+ <li>
+   <a class="dropdown-item" (click)="sendUpdates(item)"
+     >Отправить обновления</a
+   >
+ </li>
</ul>

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e636b34 and 6443e39.

📒 Files selected for processing (4)

• src/app/models/telegram.ts (1 hunks)
• src/app/modules/admin/components/telegram/stat-data-change-subscriptions/stat-data-cache-records.component.html (1 hunks)
• src/app/modules/admin/components/telegram/stat-data-change-subscriptions/stat-data-cache-records.component.ts (1 hunks)
• src/app/services/telegram-subscriptions.service.ts (1 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (1)

src/app/modules/admin/components/telegram/stat-data-change-subscriptions/stat-data-cache-records.component.ts (1)

src/app/models/telegram.ts (1)

• StatDataCacheChangeSubscription (32-43)

🔇 Additional comments (3)

src/app/models/telegram.ts (1)

39-39: LGTM: Property addition follows type conventions.

The new lastMessageSent optional field of type Date | null is appropriately placed with the other timestamp fields in the interface.

src/app/services/telegram-subscriptions.service.ts (1)

64-66: LGTM: Method implementation follows service patterns.

The new sendUpdates method follows the same structure as other API methods in this service, using a consistent pattern for HTTP requests.

src/app/modules/admin/components/telegram/stat-data-change-subscriptions/stat-data-cache-records.component.ts (1)

148-155: LGTM: Method implementation follows component patterns.

The sendUpdates method correctly:

1. Calls the service method with the item's ID
2. Uses the untilDestroyed operator for proper subscription management
3. Provides appropriate user feedback via the alert service

Note: Don't forget to add a UI element in the HTML template to trigger this method (as suggested in my HTML review).