Skip to content

Conversation

@chienyuanchang
Copy link

@chienyuanchang chienyuanchang commented Dec 8, 2025

Description

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

If an SDK is being regenerated based on a new API spec, a link to the pull request containing these API spec changes should be included above.

  • Update to get raw json for analyze_return_raw_json samples and tests
  • Update samples and sample tests based on updated .NET samples

All SDK Contribution checklist:

  • The pull request does not introduce [breaking changes]
  • CHANGELOG is updated for new features, bug fixes or other significant changes.
  • I have read the contribution guidelines.

General Guidelines and Best Practices

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

@github-actions
Copy link

github-actions bot commented Dec 8, 2025

Thank you for your contribution @chienyuanchang! We will review the pull request and get back to you soon.

# [END parse_raw_json]

# [START extract_from_raw_json]
# Extract key information from raw JSON

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we follow samples/sample_analyze_binary.py to print out markdown and equivalent document structure to show two ways to access the same functionalities?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, updated

@chienyuanchang chienyuanchang changed the title [Sample] get raw json for analyze_return_raw_json samples and tests [Sample] Updating for samples based on dotnet samples Dec 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants