-
Notifications
You must be signed in to change notification settings - Fork 333
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
refactor(app/module): minor readability improvements and more tests #3304
refactor(app/module): minor readability improvements and more tests #3304
Conversation
Warning Rate Limit Exceeded@rootulp has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 14 minutes and 6 seconds before requesting another review. How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. WalkthroughThe update primarily involves refactoring the Changes
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? TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Additionally, you can add CodeRabbit Configration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's resolve lint and i'll take a look.
p.s sorry i merged main. it's a habit
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting pattern to separate out into types and utils files. I'm not sure if I'd agree that this improves readability but I don't want to bike shed on this
…elestiaorg#3304) I was reviewing the `app/module` directory because I want to write a README for it but I noticed a few small refactors that I started working on. The refactors include: - adding more unit tests - simplify how `firstVersion` and `lastVersion` is set in the manager - extracting types to a `types.go` file - extracting utils to a `utils.go` file and adding tests - improving code comments - renaming `VersionedConfigurator` => `Configurator` - ordering public methods above private methods - renaming files to match the type they define (i.e. `manager.go`, `configurator.go`) --------- Co-authored-by: nina / ნინა <[email protected]>
…elestiaorg#3304) I was reviewing the `app/module` directory because I want to write a README for it but I noticed a few small refactors that I started working on. The refactors include: - adding more unit tests - simplify how `firstVersion` and `lastVersion` is set in the manager - extracting types to a `types.go` file - extracting utils to a `utils.go` file and adding tests - improving code comments - renaming `VersionedConfigurator` => `Configurator` - ordering public methods above private methods - renaming files to match the type they define (i.e. `manager.go`, `configurator.go`) --------- Co-authored-by: nina / ნინა <[email protected]>
I was reviewing the
app/module
directory because I want to write a README for it but I noticed a few small refactors that I started working on. The refactors include:firstVersion
andlastVersion
is set in the managertypes.go
fileutils.go
file and adding testsVersionedConfigurator
=>Configurator
manager.go
,configurator.go
)