[WEB-2442] chore: minor build fix

[rahulramesha]

This PR contains minor changes for a build fix

Summary by CodeRabbit

• Bug Fixes
  • Improved type safety for the IssueActivityStore instantiation in the IssueDetail class.

No new features or changes to existing functionality were introduced in this update.

[coderabbitai]

Walkthrough

The changes in this pull request focus on enhancing type safety within the IssueDetail class located in web/core/store/issue/issue-details/root.store.ts. A new import statement for RootStore has been added, and the instantiation of IssueActivityStore is updated to explicitly cast rootStore.rootStore as RootStore. This ensures that the type of rootStore aligns with the expected type in the IssueActivityStore constructor, while maintaining the existing logic and structure of the class.

Changes

File Path	Change Summary
web/core/store/issue/issue-details/root.store.ts	- Added import for RootStore. - Updated instantiation of IssueActivityStore to cast rootStore.rootStore as RootStore.

Possibly related PRs

• [WEB-2442] chore: Refactor timeline store #5926: The changes in the IssueActivityStore class involve a modification of the store type from RootStore to CoreRootStore, which is relevant to the main PR's focus on type safety and store interactions in the IssueDetail class.

Suggested reviewers

• SatishGandham

Poem

🐇 In the store where issues dwell,
A type was cast, all is well.
With safety now, our code will cheer,
For every bug, we hold so dear.
Hoppity hop, let changes flow,
In the land of code, we watch it grow! 🌱

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 22b616b and 5f8041a.

📒 Files selected for processing (1)

• web/core/store/issue/issue-details/root.store.ts (2 hunks)

🔇 Additional comments (2)

web/core/store/issue/issue-details/root.store.ts (2)

19-19: LGTM: Import added for type safety.

The addition of the RootStore import is necessary for the type casting and follows the existing import organization pattern.

---

198-198: LGTM: Type casting fixes build issue.

The explicit type casting of rootStore.rootStore as RootStore resolves the type mismatch that was causing the build to fail. This is a safe change as it:

1. Only affects type checking, not runtime behavior
2. Properly aligns the types between IssueActivityStore constructor and its usage

---

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.