my-phonebook_v2.0.0
Summary
April 25, 2023
- Change password feature inside the /settings page, #30
- Sidebar re-design
- Export all Contacts or selected Contacts to CSV/PDF from the sidebar Download tab, #43
- Update use-sync-v version to v2.0.16
- Upload a Contact photo when creating a new Contact or updating an existing Contact, #39, #104
- Delete a Contact photo along with Contact document deletion
- Linked profile_picture_url to actual picture from firebase
- 🆕 👉 Make Contact photos private - Store the Contact photo's Full Firebase Storage File path in the
profile_picture_url
field instead of the uploaded file's public StoragedownloadURL
- Display an option to resend the account verification email in the
- /register page - when trying to register an unverified email
- /account page - when signing in with an unverified email
- Use a stricter set of Firebase Storage Security Rules for Contact photo uploads, #50
- Display user-friendly generic Firebase permissions error messages when uploading Contact photos and creating/updating Contact documents
- Fix page errors in the /account?mode=resend_email_verification and mode=resetPassword pages
Firebase Storage Rules Updates
- Photo Image File Specifications
- The new Storage Rules accepts image files of type
.jpg
,.jpeg
,.png
,.gif
,.bmp
and.webp
- Image Files should not exceed
1 MB
(megabyte)
- The new Storage Rules accepts image files of type
- Filename
- The Firebase Storage file name should follow the pattern
photo_{docId}
without a file extension name. - For example, when uploading a "mountain.jpg" photo on Contact document
HgKAzTCzoHaIBSvqYYCAEZBO9Qp1
- Firebase Storage file name becomes
photo_HgKAzTCzoHaIBSvqYYCAEZBO9Qp1
- Firebase Storage file name becomes
- The Firebase Storage file name should follow the pattern
- Full Firebase Storage File path
- The Storage Rules only accepts a full Firebase storage file path following the pattern:
photos/{userId}/photo_{docId}
- User uploads to other paths are blocked
- Using "mountain.jpg" and the Contact document from the previous example,
- Full Firebase Storage file path becomes:
photos/XwLYjqlWbSMRJLqcwrS9wla1bzs1/photos_HgKAzTCzoHaIBSvqYYCAEZBO9Qp1
- The total Firebase Storage file path string length should not exceed
100
characters - The
{userId}
path segment refers to a signed-in user'sauthId
(uid). Users must be signed-in and have a valid Firebase Auth record:- emailVerified=true
- custom claims account_level=2
- Full Firebase Storage file path becomes:
- The Storage Rules only accepts a full Firebase storage file path following the pattern:
- Display an option to resend the account verification email in the
- /register page - when trying to register an unverified email
- /account page - when signing in with an unverified email
What's Changed
- Feature/viky 30 by @vikyw89 in #103
- export contacts UI by @vikyw89 in #105
- Feature/weaponsforge 43 by @weaponsforge in #106
- fix: bumped use-sync-v version and bug on /login by @vikyw89 in #108
- Feature/weaponsforge 39 by @weaponsforge in #109
- Update/weaponsforge 39 by @weaponsforge in #110
- Update/weaponsforge 39b by @weaponsforge in #111
- put real profile_picture on /contacts with initial as fallback by @vikyw89 in #113
- v2.0.0 by @weaponsforge in #114
Full Changelog: v1.0.6...v2.0.0