-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
StorageReference instead of Location #7
Comments
( At the application level, using fully qualified Urls for Firebase Storage is problematic if you want to be able to export/import between databases. Hence, I store relative paths and use |
I managed to get this working fairly well. I reluctantly wrapped a FutureBuilder around the FadeInImage, but since it shows the BlurHash placeholder (same as FadeInImage), it does not create the jank that I was initially worried about. I still think Firebase Storage needs to improve their API. I opened an issue for them, but I'm not holding my breathe. If they improve their API, I can improve my code. I still think there is room to revise FirebaseImage to be more StorageReference centric rather than String centric. |
You can give storage reference of folder too.
return url; Hope this is helpful for you. |
I like what you've created with FirebaseImage. I am running into a little struggle because I have a
StorageReference
to my image instead of a fully qualified location (withgs:
prefix).Would it be possible to get an overloaded version that accepts a
StorageReference
instead of the fully qualifiedlocation
?Or is there a good way to translate a
StorageReference
into a fully qualifiedlocation
? ThegetBucket
method seems like the translation, but the fact that it isasync
is a problem because I'm trying to minimize jank, so if I wrap this in aFutureBuilder
, it ends up creating jank -- it would be best to have this as part of theImageProvider
since it is already asynchronous. (I'm already usingFadeInImage
andBlurHash
to get a sweet effect.)The text was updated successfully, but these errors were encountered: