chore: reorganize IBeaconStateView interface

[wemeetagain]

reorder and reorganize IBeaconStateView

[gemini-code-assist]

Summary of Changes

Hello @wemeetagain, I'm Gemini Code Assist¹! 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 refactors the IBeaconStateView interface by reordering and categorizing its members. The primary goal is to enhance the clarity and structure of the interface, making it easier to understand and navigate. This change improves the overall maintainability of the state view by logically grouping related properties and methods, and streamlining access patterns.

Highlights

• Interface Reorganization: The IBeaconStateView interface has been extensively reordered and grouped into logical categories such as 'State access', 'Shuffling and committees', 'Validators and balances', 'Merge', 'Block production', 'API', 'Validation', 'Proofs', 'Fork choice', 'Serialization', and 'State transition' to improve readability and maintainability.
• Property and Method Streamlining: Several getter methods, such as getValidatorCount() and getActiveValidatorCount(), have been converted into direct properties (validatorCount, activeValidatorCount) for more direct and consistent access. Additionally, properties like historicalSummaries and pendingDeposits are now directly part of the interface instead of being accessed via getter methods.
• Dependency Cleanup: The ForkSeq type has been removed from imports and method signatures where it was no longer necessary, simplifying the interface and its dependencies.

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

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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

[gemini-code-assist]

Code Review

This pull request reorganizes the IBeaconStateView interface, which improves its structure and clarity. However, it introduces several breaking changes by converting methods to properties and altering method signatures. The primary implementation of this interface, BeaconStateView, has not been updated to reflect these changes, which will cause the build to fail. I have added comments highlighting the necessary updates to the implementation to align with the new interface definition. Additionally, I've suggested a minor improvement to a comment for better code maintainability.

[twoeths]

@wemeetagain I continued with your refactor:

• cache all apis requiring a "toValue()" conversion
• reorder BeaconStateView methods according to its interface
• fix compilation error

I merged to #8773 for another review