Rename files in beacon-chain/operations/slashings
#14904
Merged
+392
−389
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rkapka
force-pushed
the
rename-slashing-files
branch
from
a3ce034 to
d376e6b
Compare
rkapka
force-pushed
the
rename-slashing-files
branch
from
d376e6b to
3bab30a
Compare
nalepae
previously approved these changes
Feb 10, 2025
nalepae
approved these changes
Feb 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
Cleanup
What does this PR do? Why is it needed?
To make the diff of #14844 more readable, I added the code for the service inside
service_new.goand kept the code of the pool inservice.go. This PR cleans that up by moving the code of the pool topool.goand the code for the service toservice.go.Acknowledgements