parse linter config with cargo metadata #415
Closed
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.
Implementation for parsing out the linter config with
cargo-metadata
#334.I personally prefer deserializing the
Cargo.toml
totoml
and then parsing the metadata out over this. I can add some performance comparisons if needed, but I expect thecargo-metadata
implementation to be way slower.Some Observations:
package
that contains theworkspace
config (if present) merged with thatpackage
's config.But the
bevy_lint_driver
is called for each crate target, meaning we could build the same config multiple times.metadata
of the current package because we can not know that package's name.In this repository: https://github.com/TimJentzsch/bevy_complex_repo/tree/main
❯ cargo metadata --no-deps | jq
lists all packages in this workspace, but from where do we know which of these we should read the metadata table from?
but with
We always get the "current" package but have additional overhead.