feat: Enforce consistent style in Rust code with rustfmt #29
Conversation
This file contains hidden or 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
Member
|
Please check the conflict caused by merging #28. |
byfnoel
changed the title
Contributor
Author
|
I think now this should be fine. @parksb |
Member
|
Thank you! |
Contributor
Author
|
Thank you for merging this @parksb. Happy to see we can now further improve the CI and expand the tests we have with no major frictions. |
parksb
pushed a commit
that referenced
this pull request
Nov 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Warning
DO NOT MERGE BEFORE PR 28
This PR ensures we format all Rust Code on commits or PR. Previously, we did not have a mechanism to make sure Rust code follows conventional style guidelines.
Part of the effort for #26