Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: add v1.4.0 upgrade handler #1910

Merged
merged 2 commits into from
Jun 4, 2024
Merged

Conversation

k-yang
Copy link
Member

@k-yang k-yang commented Jun 4, 2024

Purpose / Abstract

Add v1.4.0 upgrade handler

Summary by CodeRabbit

  • New Features
    • Introduced support for version 1.4.0 upgrade, including new constants and configurations for managing the upgrade process.

@k-yang k-yang marked this pull request as ready for review June 4, 2024 18:09
@k-yang k-yang requested a review from a team as a code owner June 4, 2024 18:09
Copy link
Contributor

coderabbitai bot commented Jun 4, 2024

Walkthrough

The changes involve integrating a new upgrade version 1.4.0 into the application. This includes importing the v1_4_0 upgrade package and adding its upgrade handler and constants to the relevant files, facilitating the management of the upgrade process.

Changes

Files Change Summary
app/upgrades.go Added import for v1_4_0 upgrade and included v1_4_0.Upgrade in Upgrades.
app/upgrades/v1_4_0/... Introduced constants and configurations for the v1_4_0 upgrade.

Sequence Diagram(s) (Beta)

sequenceDiagram
    participant User
    participant App
    participant UpgradeManager
    participant v1_4_0

    User->>App: Initiate Upgrade Check
    App->>UpgradeManager: Request Available Upgrades
    UpgradeManager->>v1_4_0: Include v1_4_0 Upgrade
    v1_4_0->>UpgradeManager: Provide Upgrade Details
    UpgradeManager->>App: List of Upgrades (including v1_4_0)
    App->>User: Display Available Upgrades
Loading

Poem

In lines of code, a tale unfolds,
Version 1.4.0, a story told.
Constants set, upgrades in flight,
A smoother path, from day to night.
With every change, we rise anew,
For better code, and skies of blue.


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

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.

@k-yang k-yang self-assigned this Jun 4, 2024
@k-yang k-yang enabled auto-merge (squash) June 4, 2024 18:09
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 3a60458 and 3c04882.

Files selected for processing (2)
  • app/upgrades.go (1 hunks)
  • app/upgrades/v1_4_0/constants.go (1 hunks)
Additional context used
golangci-lint
app/upgrades.go

[error] 22-22: undefined: NibiruApp (typecheck)


[error] 27-27: undefined: NibiruApp (typecheck)


[error] 33-33: undefined: NibiruApp (typecheck)

Additional comments not posted (2)
app/upgrades/v1_4_0/constants.go (1)

12-24: The constants and upgrade handler are well-defined and align with the Cosmos SDK's upgrade pattern.

app/upgrades.go (1)

12-12: The import and addition of the v1.4.0 upgrade are correctly implemented.

Also applies to: 19-19

)

var Upgrades = []upgrades.Upgrade{
v1_1_0.Upgrade,
v1_2_0.Upgrade,
v1_3_0.Upgrade,
v1_4_0.Upgrade,
}

func (app *NibiruApp) setupUpgrades() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The type NibiruApp is undefined in this context, which could lead to runtime errors.

- func (app *NibiruApp) setupUpgrades() {
+ func (app *App) setupUpgrades() {
- func (app *NibiruApp) setUpgradeHandlers() {
+ func (app *App) setUpgradeHandlers() {
- func (app *NibiruApp) setUpgradeStoreLoaders() {
+ func (app *App) setUpgradeStoreLoaders() {

Also applies to: 27-27, 33-33

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
func (app *NibiruApp) setupUpgrades() {
func (app *App) setupUpgrades() {
```
Also applies to:
```suggestion
func (app *App) setUpgradeHandlers() {
```
```suggestion
func (app *App) setUpgradeStoreLoaders() {
Tools
golangci-lint

[error] 22-22: undefined: NibiruApp (typecheck)

Copy link

codecov bot commented Jun 4, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 62.14%. Comparing base (a5fe920) to head (3c04882).

Current head 3c04882 differs from pull request most recent head a601c6b

Please upload reports for the commit a601c6b to get more accurate results.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1910      +/-   ##
==========================================
- Coverage   62.34%   62.14%   -0.21%     
==========================================
  Files         245      245              
  Lines       15949    16010      +61     
==========================================
+ Hits         9944     9950       +6     
- Misses       5269     5323      +54     
- Partials      736      737       +1     
Files Coverage Δ
app/upgrades.go 60.00% <ø> (ø)

... and 14 files with indirect coverage changes

@k-yang k-yang merged commit bbcc6f8 into main Jun 4, 2024
9 checks passed
@k-yang k-yang deleted the chore/upgrade/v1.4.0-upgrade-handler branch June 4, 2024 20:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: ✅ Completed
Development

Successfully merging this pull request may close these issues.

3 participants