bug(cli,desktop,documentation-website,framework,history-microservice,…

[Idrinth]

…history-website,mindmap): rename all parts to new location

The Pull Request is ready

• fixes Rename name in package.json #990
• all actions are passing
• only fixes a single issue

Overview

• adjust the naming to match the new names

[coderabbitai]

Walkthrough

The assimilation process has successfully updated various package.json files, aligning package names, URLs for homepages, repositories, and issue tracking. These modifications enhance uniformity and accessibility within the repository, optimizing project management and documentation.

Changes

Files	Change Summary
cli/package.json, framework/package.json, history-microservice/package.json, mindmap/package.json	Updated package names, URLs for homepages, repositories, and issue tracking.
desktop/package.json, history-website/package.json	Added metadata including homepage, bugs URL, and repository information.
documentation-website/package.json, package.json	Modified package names and URLs; added bugs and repository fields.

Assessment against linked issues

Objective	Addressed	Explanation
Rename name in package.json (#990)	✅
Update repository URLs to follow the specified logic (#990)	✅
Point all issues to the repository's issues page (#990)	✅

🚀 A code so neat, 🌌
Across the stars, changes sweep, 🛠️
Names align, URLs refine, 📁
The collective's might, forever to keep. ✨
🐇🔧 - code of rabbit 🐇🔧

---

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:

Note: Auto-reply has been disabled for this repository by the repository owner. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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: 3

Review Details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6b7b59a and 49a1bd9.

Files ignored due to path filters (7)

• cli/package-lock.json is excluded by !**/package-lock.json
• documentation-website/package-lock.json is excluded by !**/package-lock.json
• framework/package-lock.json is excluded by !**/package-lock.json
• history-microservice/package-lock.json is excluded by !**/package-lock.json
• history-website/package-lock.json is excluded by !**/package-lock.json
• mindmap/package-lock.json is excluded by !**/package-lock.json
• package-lock.json is excluded by !**/package-lock.json

Files selected for processing (8)

• cli/package.json (1 hunks)
• desktop/package.json (1 hunks)
• documentation-website/package.json (1 hunks)
• framework/package.json (1 hunks)
• history-microservice/package.json (1 hunks)
• history-website/package.json (1 hunks)
• mindmap/package.json (2 hunks)
• package.json (2 hunks)

Files skipped from review due to trivial changes (4)

• cli/package.json
• desktop/package.json
• framework/package.json
• history-website/package.json

Additional comments not posted (12)

history-microservice/package.json (3)

2-2: The name field has been correctly updated to reflect the new naming convention.

---

8-9: The bugs URL has been correctly added for issue tracking.

---

13-13: The repository URL has been updated correctly to match the new module name.

mindmap/package.json (3)

2-2: The name field has been correctly updated to reflect the new naming convention.

---

21-22: The bugs URL has been correctly added for issue tracking.

---

26-26: The repository URL has been updated correctly to match the new module name.

package.json (3)

2-2: The name field has been correctly updated to reflect the new naming convention.

---

7-8: The bugs URL has been correctly added for issue tracking.

---

12-12: The repository URL has been updated correctly to match the new module name.

documentation-website/package.json (3)

2-2: The name field has been correctly updated to reflect the new naming convention.

---

10-11: The bugs URL has been correctly added for issue tracking.

---

15-15: The repository URL has been updated correctly to match the new module name.

[coderabbitai]

Actionable comments posted: 0

Review Details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 49a1bd9 and 2dfc13c.

Files selected for processing (2)

• framework/test/helper/user-agent.ts (1 hunks)
• package.json (2 hunks)

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

• package.json

Additional Context Used

Path-based Instructions (1)

framework/test/helper/user-agent.ts (1)

Pattern **/*.ts: Review the code for conformity with the .eslintrc files in / and /*/.

Additional comments not posted (4)

framework/test/helper/user-agent.ts (4)

14-14: The updated regular expression correctly matches the new naming convention for the framework. Well done.

---

20-20: The regular expression effectively prevents matching a '0.0' version for the framework, aligning with the intended validation logic.

---

26-26: The regular expression correctly ensures that the 'needle' version is not '0.0', which is appropriate for avoiding default or uninitialized values.

---

32-32: The regular expression effectively prevents matching a '0.0' version for 'api-bench', aligning with the intended validation logic.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[coderabbitai]

Actionable comments posted: 0

Review Details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 2dfc13c and 8ea7c1a.

Files ignored due to path filters (5)

• documentation-website/package-lock.json is excluded by !**/package-lock.json
• history-microservice/package-lock.json is excluded by !**/package-lock.json
• history-website/package-lock.json is excluded by !**/package-lock.json
• mindmap/package-lock.json is excluded by !**/package-lock.json
• package-lock.json is excluded by !**/package-lock.json

Files selected for processing (5)

• documentation-website/package.json (1 hunks)
• history-microservice/package.json (1 hunks)
• history-website/package.json (1 hunks)
• mindmap/package.json (2 hunks)
• package.json (2 hunks)

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

• documentation-website/package.json
• history-microservice/package.json
• history-website/package.json
• mindmap/package.json
• package.json