docs: use the right link for app.go[Supplementary Omission]

[GINMEL]

Similar to 21585, with some additional supplements.

Summary by CodeRabbit

• Documentation
  • Updated references in documentation from app_v2.go to app_di.go for clarity on dependency injection.
  • Revised link to the updated overview of app_di.go to ensure users have access to the latest information.

[coderabbitai]

Walkthrough

Walkthrough

This pull request updates documentation related to the SimApp package in the Cosmos SDK, specifically changing references from app_v2.go to app_di.go to reflect the new file name for the dependency injection framework. Additionally, it updates a link in the documentation for the depinject module to point to a more relevant overview. The core functionality of the SimApp package remains unchanged, with the previous implementation still accessible.

Changes

Files	Change Summary
UPGRADING.md	Renamed app_v2.go to app_di.go in the simapp package documentation.
docs/build/building-modules/15-depinject.md	Updated link from app-go-v2 to app-go-di for the app_di.go documentation overview.

Possibly related PRs

• chore: prepare core 1.0.0-alpha.1 #21564: Updates related to core versioning and module registration, potentially impacting overall structure and dependencies.
• build(deps): bump to core v1.0.0-alpha.1 and remove replaces #21603: Updates dependency to core version v1.0.0-alpha.1, relevant to dependency management discussed in the main PR.
• refactor(core): re-add handlers #21575: Re-adds handlers and modifies message handling systems, relating to the organization of the SimApp package.
• chore(all): replace all fmt.Errorf without paramters with errors.New #21590: Focuses on replacing error handling methods, contributing to overall code structure improvements.
• chore: fix spelling errors #21610: Includes minor spelling corrections, enhancing code quality and readability alongside documentation updates.

Suggested labels

C:server/v2, C:CLI

Tip

New features

Walkthrough comment now includes:

• Possibly related PRs: A list of potentially related PRs to help you recall past context.
• Suggested labels: CodeRabbit can now suggest labels by learning from your past PRs. You can also provide custom labeling instructions in the UI or configuration file.

Notes:

• Please share any feedback in the discussion post on our Discord.
• Possibly related PRs, automatic label suggestions based on past PRs, learnings, and possibly related issues require data opt-in (enabled by default).

---

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

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.

[julienrbrt]

Thank you!

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 5028893 and 50358ca.

Files selected for processing (2)

• UPGRADING.md (1 hunks)
• docs/build/building-modules/15-depinject.md (1 hunks)

Files skipped from review due to trivial changes (2)

• UPGRADING.md
• docs/build/building-modules/15-depinject.md