- Issue created by @Kristen Pol
- Issue was unassigned.
- πΊπΈUnited States Kristen Pol Santa Cruz, CA, USA
Alternatively or in addition, we could add a param to suppress the exception.
- Status changed to Postponed
6 months ago 8:56pm 4 January 2024
In some situations, rather than quant_api logging an exception, we might want to have the exception bubble up so the calling code can handle it. Example: When content is unpublished, the canonical redirect is unpublished. If the content is then deleted, there is another unpublish call for the canonical redirect which is redundant. Rather than have to check if it's already unpublished (which requires more API calls), we could simply catch and ignore these unpublish exceptions in the calling code.
Client error: `PATCH https://api.quantcdn.io/v1/unpublish` resulted in a `400 Bad Request` response: @"errorMsg":"Resource is already unpublished.","error":true
Add code to allow a bubbleUp
parameter for API functions and throw the exception (rather than log it) if bubbleUp
is TRUE. May need a new Exception class added.
Allow bubbling up exceptions to calling code.
Postponed
1.0
Code
Alternatively or in addition, we could add a param to suppress the exception.