Skip to content

Conversation

@2010YOUY01
Copy link
Contributor

Which issue does this PR close?

Part of #18503

Rationale for this change

Enforce the lint rule to all crates that are already passing this extra check, and we don't need further code change on them.

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

@github-actions github-actions bot added catalog Related to the catalog crate common Related to common crate proto Related to proto crate functions Changes to functions implementation datasource Changes to the datasource crate labels Nov 10, 2025
Copy link
Contributor

@alamb alamb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @2010YOUY01

@alamb
Copy link
Contributor

alamb commented Nov 10, 2025

I merged up and ran cargo fmt to get a clean CI

@2010YOUY01
Copy link
Contributor Author

I merged up and ran cargo fmt to get a clean CI

Thank you so much!

@2010YOUY01 2010YOUY01 added this pull request to the merge queue Nov 11, 2025
Merged via the queue into apache:main with commit 3fcbd02 Nov 11, 2025
32 checks passed
codetyri0n pushed a commit to codetyri0n/datafusion that referenced this pull request Nov 11, 2025
… require code changes. (apache#18586)

## Which issue does this PR close?

<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases.
You can link an issue to this PR using the GitHub syntax. For example
`Closes apache#123` indicates that this PR will close issue apache#123.
-->

Part of apache#18503

## Rationale for this change

<!--
Why are you proposing this change? If this is already explained clearly
in the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand
your changes and offer better suggestions for fixes.
-->
Enforce the lint rule to all crates that are already passing this extra
check, and we don't need further code change on them.

## What changes are included in this PR?

<!--
There is no need to duplicate the description in the issue here but it
is sometimes worth providing a summary of the individual changes in this
PR.
-->

## Are these changes tested?

<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code

If tests are not included in your PR, please explain why (for example,
are they covered by existing tests)?
-->

## Are there any user-facing changes?

<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->

<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->

Co-authored-by: Andrew Lamb <andrew@nerdnetworks.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

catalog Related to the catalog crate common Related to common crate datasource Changes to the datasource crate functions Changes to functions implementation proto Related to proto crate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants