this is the screen which am trying to develop, in which am trying to point to the location on the map then record its information, plus three images to describe it, the data will be saved in firebase, and the images in cloudinary, but i was hoping the be able to upload and delete images, uploading was easy but the delete part was the very difficult part
When you have the Base64 string and you store it in any kind of storage then viewing it is as simple as retrieving the string and assigning it to an image component because it accepts Base64 directly to be the image to display.
This way, you store the Base64 in the table and you do not need to convert it to image again.
Thank you very much muneer for the example. it makes it very clear. the concept is simple…
my problem with Cloudinary is the deleting part because I have to send the image to Cloudinary then retrieving back the URL, display it, and then delete it. also there is a problem of making custom Public Id, to be honest, I don’t know how to do that part especially when am using media upload component, not web api.
There’s always more than 1 way for the cookie to crumble. The solution I shared opens doors for when our file picker/base64 converter is released! I also plan to show how to make authenticated calls to firestore and a few other things.
Also, if hashify ever stops working, we’ll need a another solution.
I plan to document both approaches eventually so we dont have to sort through forum posts