Use more robust JSON parsing rather than regex and string matching

Devin Martin avatarDevin Martin created an issue

The current implementation works, but is quite brittle. Replace the current string.Contains and Regex.Match calls with full JSON parsing. In most cases the production API seems to use the fields passed into the API as field names in the response object when there is a problem so it should be a bit more robust to look for specific fields on the response JSON object, rather than match specific text.

Comments (0)

  1. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.