Skip to content

my-phonebook_v2.0.0
Compare
Choose a tag to compare
@weaponsforge weaponsforge released this 25 Apr 12:32
· 35 commits to master since this release
v2.0.0
6dc931b
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

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 Storage downloadURL
  • 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)
  • 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
  • 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's authId (uid). Users must be signed-in and have a valid Firebase Auth record:
        • emailVerified=true
        • custom claims account_level=2
  • 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

Full Changelog: v1.0.6...v2.0.0

Contributors

weaponsforge and vikyw89
Assets 2
Loading