Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
sql: Fix
generate_extracted_config!
macro for rust-analyzer (#30004)
This PR updates the `generate_extracted_config!` macro so rust-analyzer no longer shows errors for invocations of the macro. The issue was rust-analyzer was resolving traits implementations incorrectly so we fully qualify some trait method calls to help it out. This makes the macro a bit less flexible by requiring the `value` field of a SQL `WITH` option be an `Option<WithOptionValue<T>>`, but all uses of it today are exactly that type, so I don't anticipate any issue. ### Motivation * This PR fixes a previously unreported bug. rust-analyzer (used in IDEs) would show an error for invocations of this macro, even though the code compiled without issue. ### Checklist - [x] This PR has adequate test coverage / QA involvement has been duly considered. ([trigger-ci for additional test/nightly runs](https://trigger-ci.dev.materialize.com/)) - [x] This PR has an associated up-to-date [design doc](https://github.com/MaterializeInc/materialize/blob/main/doc/developer/design/README.md), is a design doc ([template](https://github.com/MaterializeInc/materialize/blob/main/doc/developer/design/00000000_template.md)), or is sufficiently small to not require a design. <!-- Reference the design in the description. --> - [x] If this PR evolves [an existing `$T ⇔ Proto$T` mapping](https://github.com/MaterializeInc/materialize/blob/main/doc/developer/command-and-response-binary-encoding.md) (possibly in a backwards-incompatible way), then it is tagged with a `T-proto` label. - [x] If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label ([example](MaterializeInc/cloud#5021)). <!-- Ask in #team-cloud on Slack if you need help preparing the cloud PR. --> - [x] If this PR includes major [user-facing behavior changes](https://github.com/MaterializeInc/materialize/blob/main/doc/developer/guide-changes.md#what-changes-require-a-release-note), I have pinged the relevant PM to schedule a changelog post.
- Loading branch information