Skip to content

Docs/add parse json examples #2338

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

karthikmanam
Copy link
Contributor

Explanation

This PR adds clear examples for the parse_json and to_boolean functions in the JP documentation. Previously, these documentation pages only contained a placeholder "TODO" instead of actual examples, making it difficult for users to understand how to use these functions properly. This PR represents an addition to the existing documentation to improve its completeness and usefulness.

Related issue

This is a documentation improvement to address incomplete function examples. No specific issue is being fixed, but it contributes to the overall documentation quality of the project.

Proposed Changes

  • Added comprehensive examples for the parse_json function showing how to:
    • Parse JSON objects and access their properties
    • Parse JSON arrays and access elements
    • Parse nested JSON structures
  • Added examples for the to_boolean function demonstrating:
    • Case insensitivity (true/True/TRUE)
    • Handling of various string formats for boolean values

Checklist

Signed-off-by: Karthik babu Manam <karthikmanam@gmail.com>
@karthikmanam karthikmanam force-pushed the docs/add-parse-json-examples branch from d6ea6bb to 307cba9 Compare April 1, 2025 06:36
@karthikmanam karthikmanam marked this pull request as ready for review April 1, 2025 06:41
@karthikmanam karthikmanam requested a review from a team as a code owner April 1, 2025 06:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants