P-Token Formatting #83
Merged
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
Collaborator
Author
|
The diff is big and goes across a lot of files, I did read it all to check that it was indeed only changes in formatting (whitespace and newlines etc.) |
dkcumming
requested review from
JuanCoRo,
Stevengre,
jberthold,
sskeirik and
tothtamas28
tothtamas28
approved these changes
Nov 3, 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.
#77 Applied linting, but did not apply formatting
Formatting is checked with:
This pr also creates a CI job that will check linting and formatting for PRs to proof branch.
Again this does not apply to SPL-Token which @Stevengre and I will deal with at a later point