Add debug logging support to Rust client generator#21714
Closed
gfx wants to merge 1 commit intoOpenAPITools:masterfrom
Closed
Add debug logging support to Rust client generator#21714gfx wants to merge 1 commit intoOpenAPITools:masterfrom
gfx wants to merge 1 commit intoOpenAPITools:masterfrom
Conversation
Member
|
thanks for the PR please follow step 3 in the PR checklist to update the samples so that the CI can verify the change |
Author
|
Will do it later. For now, I'll make a custom template file for my project. |
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
2 participants
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.
This PR adds debug logging capabilities to the Rust client generator. The changes enable developers to debug API calls by logging HTTP method and URI information.
Changes:
tracingdependency (^0.1) to the Rust client Cargo.toml templateThis enhancement helps developers troubleshoot API interactions by providing visibility into the actual HTTP requests being made by the generated Rust client code.
Ideally, a configuration, such as
trace: "info" | "debug", should be added, but for now,debug!will work for me (and most of pepole).