Add markdown output support - #64
Merged
Merged
Conversation
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
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.
Summary
Search results can now be returned as Markdown by setting
params.outputto"md". JSON remains the default for this release, so existing clients keep the same behavior.Changes
params.output="md".output="json"requests as JSON.output="json".0.5.0to0.6.0.mode=compactkeeps markdown unaltered.Fixes
Previously, passing an
output=htmlparam to tool requests caused an.as_dict()conversion error because the SDK returned raw HTML as a string. This is now clearly shown as a format error:The search tool now accepts only
"json"and"md". Other values are rejected before the request with:Testing
"output": "md"result:Request:

Response:

Response from Amazon engine:
