Prefactor tffmt to be friendlier to upcoming changes
#16966
Merged
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
thejcannon
added
the
category:internal
Eric-Arellano
approved these changes
Sep 22, 2022
tdyas
reviewed
Sep 22, 2022
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.
Formatters will get dedicated partitioning rules just like
lintin an upcoming PR. This change essentially makes thetffmtcode look very close to how it'll look in that PR.Mainly:
style.pyhas been renamed topartition.pyand greatly strippedtffmt.pycore rule now shells out to 2 helper rules (suspiciously looking like the upcoming PRs)[ci skip-rust]
[ci skip-build-wheels]