While looking into #462, I noticed that I was unable to upload the associated assurance case (attached here for convenience).
@cptanalatriste was able to locate the source of the issue as some trailing commas in the json, but no error message was provided to the user. It was only discoverable through the developer console.
May need to convert this into a user story, but logging this as a bug for now, as I'm not sure how the trailing commas got there in the first place. The original json file was exported from the TEA platform, so no trailing commas should have been added.
While looking into #462, I noticed that I was unable to upload the associated assurance case (attached here for convenience).
@cptanalatriste was able to locate the source of the issue as some trailing commas in the json, but no error message was provided to the user. It was only discoverable through the developer console.
May need to convert this into a user story, but logging this as a bug for now, as I'm not sure how the trailing commas got there in the first place. The original json file was exported from the TEA platform, so no trailing commas should have been added.
Example.Case.for.Homepage-2024-5-6T11-0-9.json