You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The paths in firebase.storage.Native are inconsistent – it would be nice if they were all either with or without trailing slashes, in order to simplify building file paths to local resources.
firebase.storage.Native.TEMP_DIRECTORY_PATHhas a trailing slash. firebase.storage.Native.DOCUMENT_DIRECTORY_PATHdoes not have a trailing slash.
In addition to these things, TEMP_DIRECTORY_PATH is listed as TEMPORARY_DIRECTORY_PATH, but isn’t available as a property in firebase.storage.Native.
Environment
Application Target Platform: iOS
Development Operating System: macOS High Sierra
Build Tools: Xcode 9.3
React Native version: 0.55.3
RNFirebase Version: 4.2.0
Firebase Module: Storage
The text was updated successfully, but these errors were encountered:
We're aware that Storage has fallen behind slightly on React Native Firebase and would like to bring it up to speed again. I will close this issue for now and track it as well as other issues collectively over on the Storage improvements proposal to be addressed in a future release. See #1260
Have just fixed this pending v4.3.0 release. For consistency all paths have been changed to be without a trailing slash as this was the least breaking change. Additionally TEMP_DIRECTORY_PATH was missing on android and has been added, was already there on iOS.
Issue
The paths in
firebase.storage.Native
are inconsistent – it would be nice if they were all either with or without trailing slashes, in order to simplify building file paths to local resources.firebase.storage.Native.TEMP_DIRECTORY_PATH
has a trailing slash.firebase.storage.Native.DOCUMENT_DIRECTORY_PATH
does not have a trailing slash.In addition to these things,
TEMP_DIRECTORY_PATH
is listed asTEMPORARY_DIRECTORY_PATH
, but isn’t available as a property infirebase.storage.Native
.Environment
The text was updated successfully, but these errors were encountered: