Implement Logging Levels for Supportability, Fixes for Prerecorded Response Types #194
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 implements:
During logging implementation, I found the following issues in the
prerecorded/v1/response.py
classes, causing parsing failures in certain rare situations. The class and properties layout mimic the Go SDK for optional parameters with default values required bydataclasses_json
.Tested to make sure all examples work as expected.
examples/manage/balances
andexamples/prerecorded/file
show examples of how to enable the highest level of verbosity for logging (SPAM
).TODO: Need to figure out a way to reduce the output... the issue is the
blah.blah.blah
notation causes 3 invocations of accessing the property a single time.Example output for
balances
: