gsh build list --json outputs unparsable JSON

Open
#2 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
48/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
csharp
Domain
cli

Research direction

Reproduce the issue with gsh build list --json --version 1.0.0 and inspect the build-list JSON output path. Ensure an empty Ccd field does not produce an extra comma, then verify that the command emits valid JSON.

Written by the indexing model from the issue text.

Description

bug

Using --version 1.0.0

[
  {
    "BuildName": "XXXXXX",
    "BuildId": XXXXX,
    "OsFamily": "LINUX",
    "Updated": "2023-08-23T16:43:44Z",
    "BuildConfigurations": 0,
    "SyncStatus": "PENDING",
    "Ccd": {
      "BucketId": "XXXXXX",,      "ReleaseId": "00000000-0000-0000-0000-000000000000"
    },
    "Container": null,
    "S3": null
  }
]

see
"BucketId": "XXXXXX",, "Re
empty field.

Dominant language
C#
Stars
47
Forks
15
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Unity-Technologies/unity-gaming-services-cli

All issues in Unity-Technologies/unity-gaming-services-cli

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.