refactor: introduce influxdb3_types crate #25946
Open
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.
Fixes #24672
...partially. It doesn't completely move all request/response types into the new crate. In particular, it leaves out all the
*Builder
types in theinfluxdb3_client
crate, ie:These builder types look like they are intended to produce the effect of a fluent interface for the
influxdb3_client::Client
type with typical usage that looks like:To achieve this effect, these builder types hold a reference to the
Client
itself, which means they can't easily be migrated outside of this module without significantly refactoring away from this fluent approach to making certain kinds of request.What this PR does do:
influxdb3_types
crateinfluxdb3_client
crateDELETE
http method was being used wherePOST
was expected for/api/v3/configure/plugin_environment/install_packages
and/api/v3/configure/plugin_environment/install_requirements