github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-22 12:32:53 -05:00
Code Issues 144 Packages Projects Releases 93 Wiki Activity

[PR #4284] [MERGED] [PM-14553] Make canManage property of collections optional #4832

New Issue
Closed
opened 2025-11-26 23:50:23 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-26 23:50:23 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/bitwarden/android/pull/4284
Author: @SaintPatrck
Created: 11/11/2024
Status: ✅ Merged
Merged: 11/14/2024
Merged by: @SaintPatrck

Base: main ← Head: PM-14553/make-manage-optional

📝 Commits (3)

  • f91321a [PM-14553] Default canManage to true for non-readonly collections
  • fd84b76 Update database to support nullable canManage for collections
  • 289fb9c Merge branch 'main' into PM-14553/make-manage-optional

📊 Changes

6 files changed (+285 additions, -4 deletions)

View changed files

➕ app/schemas/com.x8bit.bitwarden.data.vault.datasource.disk.database.VaultDatabase/6.json (+256 -0)
📝 app/src/main/java/com/x8bit/bitwarden/data/vault/datasource/disk/database/VaultDatabase.kt (+1 -1)
📝 app/src/main/java/com/x8bit/bitwarden/data/vault/datasource/disk/entity/CollectionEntity.kt (+1 -1)
📝 app/src/main/java/com/x8bit/bitwarden/data/vault/datasource/network/model/SyncResponseJson.kt (+1 -1)
📝 app/src/main/java/com/x8bit/bitwarden/data/vault/repository/util/VaultSdkCollectionExtensions.kt (+1 -1)
📝 app/src/test/java/com/x8bit/bitwarden/data/vault/repository/util/VaultSdkCollectionExtensionsTest.kt (+25 -0)

📄 Description

🎟️ Tracking

PM-14553

📔 Objective

This change updates the database schema to allow the canManage property of collections to be nullable. It also updates the data source implementation to handle the nullable value.

If the canManage property is not specified for a collection, assume it is true for non-readonly collections. This ensures that users can manage collections that are not read-only, if the canManage property is not explicitly set.

⏰ Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation or informed the documentation team

🦮 Reviewer guidelines

  • 👍 (:+1:) or similar for great changes
  • 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
  • ❓ (:question:) for questions
  • 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed
    issue and could potentially benefit from discussion
  • 🎨 (:art:) for suggestions / improvements
  • ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
  • 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
  • ⛏ (:pick:) for minor or nitpick changes

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/bitwarden/android/pull/4284 **Author:** [@SaintPatrck](https://github.com/SaintPatrck) **Created:** 11/11/2024 **Status:** ✅ Merged **Merged:** 11/14/2024 **Merged by:** [@SaintPatrck](https://github.com/SaintPatrck) **Base:** `main` ← **Head:** `PM-14553/make-manage-optional` --- ### 📝 Commits (3) - [`f91321a`](https://github.com/bitwarden/android/commit/f91321a35597eeeded25798263021aa46fd45a11) [PM-14553] Default canManage to true for non-readonly collections - [`fd84b76`](https://github.com/bitwarden/android/commit/fd84b762d0c6b136c4724c5d700b099ab0dbe618) Update database to support nullable canManage for collections - [`289fb9c`](https://github.com/bitwarden/android/commit/289fb9c4bc27be438003c9f619f11c91956543e6) Merge branch 'main' into PM-14553/make-manage-optional ### 📊 Changes **6 files changed** (+285 additions, -4 deletions) <details> <summary>View changed files</summary> ➕ `app/schemas/com.x8bit.bitwarden.data.vault.datasource.disk.database.VaultDatabase/6.json` (+256 -0) 📝 `app/src/main/java/com/x8bit/bitwarden/data/vault/datasource/disk/database/VaultDatabase.kt` (+1 -1) 📝 `app/src/main/java/com/x8bit/bitwarden/data/vault/datasource/disk/entity/CollectionEntity.kt` (+1 -1) 📝 `app/src/main/java/com/x8bit/bitwarden/data/vault/datasource/network/model/SyncResponseJson.kt` (+1 -1) 📝 `app/src/main/java/com/x8bit/bitwarden/data/vault/repository/util/VaultSdkCollectionExtensions.kt` (+1 -1) 📝 `app/src/test/java/com/x8bit/bitwarden/data/vault/repository/util/VaultSdkCollectionExtensionsTest.kt` (+25 -0) </details> ### 📄 Description ## 🎟️ Tracking PM-14553 ## 📔 Objective This change updates the database schema to allow the `canManage` property of collections to be nullable. It also updates the data source implementation to handle the nullable value. If the `canManage` property is not specified for a collection, assume it is true for non-readonly collections. This ensures that users can manage collections that are not read-only, if the canManage property is not explicitly set. ## ⏰ Reminders before review - Contributor guidelines followed - All formatters and local linters executed and passed - Written new unit and / or integration tests where applicable - Used internationalization (i18n) for all UI strings - CI builds passed - Communicated to DevOps any deployment requirements - Updated any necessary documentation or informed the documentation team ## 🦮 Reviewer guidelines <!-- Suggested interactions but feel free to use (or not) as you desire! --> - 👍 (`:+1:`) or similar for great changes - 📝 (`:memo:`) or ℹ️ (`:information_source:`) for notes or general info - ❓ (`:question:`) for questions - 🤔 (`:thinking:`) or 💭 (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion - 🎨 (`:art:`) for suggestions / improvements - ❌ (`:x:`) or ⚠️ (`:warning:`) for more significant problems or concerns needing attention - 🌱 (`:seedling:`) or ♻️ (`:recycle:`) for future improvements or indications of technical debt - ⛏ (`:pick:`) for minor or nitpick changes --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-26 23:50:23 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#4832
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?