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

feat: move v2 as default in the move cmd #309

Merged
merged 1 commit into from
Nov 22, 2024
Merged

Conversation

beer-1
Copy link
Contributor

@beer-1 beer-1 commented Nov 22, 2024

Description

Change default move version to v2 in move cmd.


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title, you can find examples of the prefixes below:
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

@beer-1 beer-1 self-assigned this Nov 22, 2024
@beer-1 beer-1 requested a review from a team as a code owner November 22, 2024 02:39
Copy link

coderabbitai bot commented Nov 22, 2024

📝 Walkthrough

Walkthrough

The changes in this pull request focus on the cmd/move/move.go file, specifically updating the default values for the flagCompilerVersion and flagLanguageVersion from "1" to "2". This adjustment reflects a transition to newer versions of the Move compiler and language specifications. The modifications also include updates to the addMoveBuildFlags function to align with these changes, while maintaining the overall structure and functionality of existing command definitions and error handling mechanisms.

Changes

File Change Summary
cmd/move/move.go Updated default values for flagCompilerVersion and flagLanguageVersion from "1" to "2"; modified addMoveBuildFlags function to reflect these changes.

Possibly related PRs

  • bump move to latest #262: This PR modifies the cmd/move/move.go file by changing the data types of the flagCompilerVersion and flagLanguageVersion flags from Uint32 to String, which directly relates to the changes made in the main PR regarding the flag definitions.

Poem

🐇 In the land of Move, a change so bright,
Flags now set to version two, what a sight!
With every build and test, we hop along,
Our commands stay strong, where we belong.
So let's cheer for updates, both swift and true,
In the world of coding, we’ll always renew! 🌟


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between a58daf9 and 30afbf5.

📒 Files selected for processing (1)
  • cmd/move/move.go (1 hunks)
🔇 Additional comments (1)
cmd/move/move.go (1)

581-582: LGTM! Default version updated to v2.

The changes align with the PR objective by updating both compiler and language versions to "2" as the default.

Let's verify that these defaults are properly integrated:

✅ Verification successful

Default version update to v2 is properly integrated

The verification confirms that:

  • The flags are correctly defined and used in the getBuildConfig function
  • The version values are properly passed to buildtypes.WithCompilerVersion and buildtypes.WithLanguageVersion
  • The "1" reference found in x/mstaking/client/cli/tx.go is unrelated (it's for defaultMinSelfDelegation)
  • The changes are consistent and properly integrated into the build configuration system
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the version flags are properly used in the codebase
# Test: Search for any hardcoded version "1" references that might need updating
rg -l '"1"' | grep -v "test"

# Test: Verify the flag usage in build configuration
ast-grep --pattern 'buildtypes.WithCompilerVersion($version)'
ast-grep --pattern 'buildtypes.WithLanguageVersion($version)'

Length of output: 320


Script:

#!/bin/bash
# Let's check the actual usage of these flags in the move.go file
rg -A 5 "flagCompilerVersion|flagLanguageVersion" cmd/move/move.go

# Also check if there are any other version-related configurations in move.go
ast-grep --pattern 'buildtypes.BuildConfig{
  $$$
}'

# Check the content of x/mstaking/client/cli/tx.go for version "1" usage context
rg -A 5 '"1"' x/mstaking/client/cli/tx.go

Length of output: 1546


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

Copy link

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

PackageVersionScoreDetails

Scanned Files

Copy link

codecov bot commented Nov 22, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 41.11%. Comparing base (a58daf9) to head (30afbf5).
Report is 2 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main     #309   +/-   ##
=======================================
  Coverage   41.11%   41.11%           
=======================================
  Files         268      268           
  Lines       25682    25682           
=======================================
  Hits        10559    10559           
  Misses      13486    13486           
  Partials     1637     1637           
---- 🚨 Try these New Features:

Copy link
Contributor

@Vritra4 Vritra4 left a comment

Choose a reason for hiding this comment

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

LGTM

@beer-1 beer-1 merged commit 7930a8a into main Nov 22, 2024
12 checks passed
@beer-1 beer-1 deleted the feat/make-v2-as-default branch November 22, 2024 04:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants