chore: some .toml files had divergent description, edition, or version fields - #3969
Open
hippietrail wants to merge 3 commits into
Open
chore: some .toml files had divergent description, edition, or version fields#3969hippietrail wants to merge 3 commits into
.toml files had divergent description, edition, or version fields#3969hippietrail wants to merge 3 commits into
Conversation
…`version` fields When setting up my new `posslq` package I wanted to make sure I set up the fields of its `.toml` file matching the other `.toml`s in the repo. I wrote a little tool to compare them. (Let me know if you want me to share it or add it to Harper's build tests.) The tool found five `.toml` files with fields that didn't match most others in the repo. It only checks for values that don't fit the pattern, it doesn't check for missing keys or extra keys in comparison to the overall average. Let me know if I should add this.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Issues
N/A
Description
When setting up my new
posslqpackage I wanted to make sure I set up the fields of its.tomlfile matching the other.tomls in the repo.I wrote a little tool to compare them. (Let me know if you want me to share it or add it to Harper's build tests.)
The tool found five
.tomlfiles with fields that didn't match most others in the repo.It only checks for values that don't fit the pattern, it doesn't check for missing keys or extra keys in comparison to the overall average. Let me know if I should add this.
Let me know if any of these values were specifically not matching the others on purpose for some reason.
How Has This Been Tested?
cargo testAI Disclosure
Well I did use AI help to make the tool that I found these apparent anomalies with, but I changed the
tomlfiles myself.Checklist