@daroczig Good catch - this is because tryCatch changes scope, and newResponse can't apparently find the correct function to look up the response type from. Need to meditate on if this is worth being clever around building wrapper objects, and/or should just throw a nicer error than "type not found".
@daroczig Good catch - this is because tryCatch changes scope, and newResponse can't apparently find the correct function to look up the response type from. Need to meditate on if this is worth being clever around building wrapper objects, and/or should just throw a nicer error than "type not found".