chore(primitives): dropped primitives service types

[abi87]

unused, seems leftovers from a previous iteration

Summary by CodeRabbit

• New Features

  • No new features added in this release.

• Bug Fixes

  • No bug fixes included in this release.

• Chores

  • Removed obsolete type aliases for messages related to slot and status events.
  • Deleted the service status management implementation, streamlining the codebase.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 22.24%. Comparing base (05ce9dc) to head (980b48c).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2063      +/-   ##
==========================================
+ Coverage   22.22%   22.24%   +0.01%     
==========================================
  Files         357      356       -1     
  Lines       16043    16034       -9     
  Branches       12       12              
==========================================
  Hits         3566     3566              
+ Misses      12325    12316       -9     
  Partials      152      152              

[coderabbitai]

Walkthrough

The changes involve modifications to the types.go file in the mod/node-core/pkg/components package, where two type aliases, SlotMessage and StatusMessage, have been removed. Additionally, the import statement for the service package has been eliminated. Furthermore, the status.go file within the mod/primitives/pkg/service package has been deleted, which included the definition of the StatusEvent struct and its associated methods and constructor.

Changes

File Path	Change Summary
mod/node-core/pkg/components/types.go	Removed type aliases SlotMessage and StatusMessage, and deleted the import statement for service.
mod/primitives/pkg/service/status.go	Deleted the entire file, which included the StatusEvent struct and its associated methods.

Possibly related PRs

• chore(encoding): dropped go-json direct dependency #2033: The removal of the StatusMessage type alias in the main PR is related to the deletion of the StatusEvent type in PR chore(encoding): dropped go-json direct dependency #2033, as both involve changes to the service package and its types.

Suggested reviewers

• nidhi-singh02
• ocnc
• itsdevbear

🐇 In the code we hop and play,
Removing types to clear the way.
With SlotMessage gone, and Status too,
The path is bright for something new!
Let's dance through changes, swift and light,
For in this code, all feels just right! 🌟

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Files that changed from the base of the PR and between 05ce9dc and 980b48c.

📒 Files selected for processing (2)

• mod/node-core/pkg/components/types.go (0 hunks)
• mod/primitives/pkg/service/status.go (0 hunks)

💤 Files with no reviewable changes (2)

• mod/node-core/pkg/components/types.go
• mod/primitives/pkg/service/status.go

---

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