-
Notifications
You must be signed in to change notification settings - Fork 227
ADD readme for APIViewJSON Utility #9270
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
Merged
praveenkuttappan
merged 2 commits into
Azure:main
from
praveenkuttappan:token_utility_doc
Oct 30, 2024
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,34 @@ | ||
| # APIViewJsonUtility | ||
|
|
||
| ### Overview | ||
|
|
||
| APIViewJsonUtility is a .NET utility designed to facilitate the manipulation and processing of JSON data within the APIView ecosystem. This tool helps developers to efficiently handle JSON data structures, making it easier to integrate with APIView's functionalities when working on parser to verify how JSON token file is rendered as output text on APIView without uploading JSON file to APIView. | ||
|
|
||
| ### Features | ||
|
|
||
| - **Create API view output from JSON token**: Parse JSON token file to create the API review output text. | ||
| - **Convert to tree token model**: Convert an old flat list tree token JSON file to new tree style JSON token file. | ||
|
|
||
|
|
||
| ### Prerequisites | ||
|
|
||
| - .NET SDK (version 8.0 or later) | ||
|
|
||
| ### Installation | ||
|
|
||
| APIViewJsonUtility is published to Azure DevOps artifact. You can install this .NET tool from [azure-sdk-for-net feed](https://dev.azure.com/azure-sdk/public/_artifacts/feed/azure-sdk-for-net/NuGet/APIViewJsonTool/overview) using below command. | ||
|
|
||
| `dotnet tool install --add-source "https://pkgs.dev.azure.com/azure-sdk/public/_packaging/azure-sdk-for-net/nuget/v3/index.json" --version 1.0.0-dev.20240919.3 --tool-path <installation path> APIViewJsonTool | ||
| ` | ||
|
|
||
| ### Usage | ||
|
|
||
| Here are two examplea of how to use APIViewJsonUtility: | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. examples |
||
|
|
||
| - Create APIView output text | ||
|
|
||
| `.\APIViewJsonUtility.exe --path <Path to JSON tree token file> --dumpApiText` | ||
|
|
||
| - Convert Token file to tree model from flat list JSON | ||
|
|
||
| `.\APIViewJsonUtility.exe --path <Path to flat list JSON token file> --convertToTree` | ||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would it be better to just say
<version>instead of us hardcoding a version here? I wonder if someone is not paying attention, they will just copy the command and might not get the latest version