Certain endpoints return a 200 status but are actually failures

[clo4]

I’ve already let Jamf School know about this by email, so until it’s fixed all I can do is work around this on my end.

There are 2 options:

1. Do nothing (ignore the issue)
2. Wrap the assertValid call in a try/catch that, on failure, will check if the JSON has a code property, and will run through the afterResponse checks again. This means I might need to abstract away the logic of the afterResponse hooks.

Option 2 is more complicated, but I feel like I might end up sticking with option 1. I’ll keep this issue open to track it though.