Due to the nature of the cloudinary widget mechanism. When clicking on the assigned button, an entire new widget is launched each time. Whilst the performance impact is negligible, it meant that sources like google drive would need to be authenticated for every new widget you opened. To mitigate this the following has been added,
after calling for a new widget 'createUploadWidget', it is assigned to window and therefore is able to accessed globally within the dom.
due to restrictions enforced by cloudinary, the widget has an 'update' method but you are not able to update the callbacks, so any new uploads would revert back to the component where the widget was originally created. onSuccess and onFailure are also now assigned to window under 'cloudinaryOn(success or failure)callback' and new opens of the widget will return responses to the expected location.
Due to the nature of the cloudinary widget mechanism. When clicking on the assigned button, an entire new widget is launched each time. Whilst the performance impact is negligible, it meant that sources like google drive would need to be authenticated for every new widget you opened. To mitigate this the following has been added,