Skip to content

chore: move utils/validator.zigvalidator.zig#321

Open
markolazic01 wants to merge 1 commit intoChainSafe:mainfrom
markolazic01:chore/move-validator-out-of-utils
Open

chore: move utils/validator.zigvalidator.zig#321
markolazic01 wants to merge 1 commit intoChainSafe:mainfrom
markolazic01:chore/move-validator-out-of-utils

Conversation

@markolazic01
Copy link
Copy Markdown

chore: move utils/validator.zigvalidator.zig

Part of #169

Changes

  • Moved src/state_transition/utils/validator.zig to src/state_transition/validator.zig
  • Updated all import paths across block/, epoch/, slot/, cache/, and utils/ to reference the new location
  • Updated internal imports within validator.zig itself (EpochCache, hasCompoundingWithdrawalCredential) to reflect the new directory level
  • Removed the reference from utils_test_root.zig, consistent with how previous moves in this effort were handled

Builds and compiles cleanly.

AI disclosure: Claude was consulted for reviewing the diff and drafting this description. All code changes were authored manually.

@markolazic01 markolazic01 requested a review from a team as a code owner April 21, 2026 19:07
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request performs a structural refactoring by moving the validator utility file to a higher-level directory within the state transition module. This change necessitates updating numerous import paths throughout the project to ensure consistency and maintainability. The move is part of a broader effort to organize the codebase more effectively.

Highlights

  • File Relocation: Moved src/state_transition/utils/validator.zig to src/state_transition/validator.zig to improve project structure.
  • Import Path Updates: Updated all import references across the codebase to point to the new location of validator.zig.
  • Internal Refactoring: Adjusted internal imports within validator.zig to maintain correct module resolution and removed the obsolete test reference.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request refactors the project structure by moving validator.zig from the utils directory to the parent state_transition directory, which required updating import paths across numerous files. A review comment identifies a style guide violation in the moved validator.zig file where an import line exceeds the 100-column limit.

const EpochCache = @import("./cache/epoch_cache.zig").EpochCache;
const WithdrawalCredentials = types.primitive.Root.Type;
const hasCompoundingWithdrawalCredential = @import("./electra.zig").hasCompoundingWithdrawalCredential;
const hasCompoundingWithdrawalCredential = @import("./utils/electra.zig").hasCompoundingWithdrawalCredential;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

This line exceeds the 100-column limit specified in the repository style guide. Please wrap the import to adhere to the typographic measure constraints.

const electra_utils = @import("./utils/electra.zig");
const hasCompoundingWithdrawalCredential = electra_utils.hasCompoundingWithdrawalCredential;
References
  1. Hard limit all line lengths, without exception, to at most 100 columns for a good typographic 'measure'. Use it up. Never go beyond. (link)

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Seems like an unrelated change request as the repo generally does not follow this rule, I guess it should be formatted as a whole some time later.
Will leave as is.

@GrapeBaBa
Copy link
Copy Markdown
Contributor

@markolazic01 thanks for contribution, refer to #187 currently paused, try to pick other task

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