It appears, that Vault 2 checks the revision to know whether it should update the cipher data. This change updates user's revision when major changes like collection access change occurs. This way the user can see proper ciphers as he gained/lost access to them without logging off and back in.
🔄 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/dani-garcia/vaultwarden/pull/144
**Author:** [@mprasil](https://github.com/mprasil)
**Created:** 8/21/2018
**Status:** ✅ Merged
**Merged:** 8/21/2018
**Merged by:** [@dani-garcia](https://github.com/dani-garcia)
**Base:** `beta` ← **Head:** `collection_revision`
---
### 📝 Commits (1)
- [`a5ef8ae`](https://github.com/dani-garcia/vaultwarden/commit/a5ef8aef0f7e6051578fc8138ec7dc627808aa40) Update affected users revision when there are collection changes
### 📊 Changes
**2 files changed** (+20 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `src/db/models/collection.rs` (+12 -0)
📝 `src/db/models/user.rs` (+8 -0)
</details>
### 📄 Description
It appears, that Vault 2 checks the revision to know whether it should update the cipher data. This change updates user's revision when major changes like collection access change occurs. This way the user can see proper ciphers as he gained/lost access to them without logging off and back in.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/dani-garcia/vaultwarden/pull/144
Author: @mprasil
Created: 8/21/2018
Status: ✅ Merged
Merged: 8/21/2018
Merged by: @dani-garcia
Base:
beta← Head:collection_revision📝 Commits (1)
a5ef8aeUpdate affected users revision when there are collection changes📊 Changes
2 files changed (+20 additions, -0 deletions)
View changed files
📝
src/db/models/collection.rs(+12 -0)📝
src/db/models/user.rs(+8 -0)📄 Description
It appears, that Vault 2 checks the revision to know whether it should update the cipher data. This change updates user's revision when major changes like collection access change occurs. This way the user can see proper ciphers as he gained/lost access to them without logging off and back in.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.