Open
Conversation
Owner
Author
|
Additionally a nested/flat mode is added, so one can decide if the backup should be better browseable with keepass groups for folders/collections of organizations or better searchable without duplicate entries. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There was a problem for organization items: If the item had a folder, the items would appear in the groups outside of the organization. Additionally, no folders were created in the organization.
This PR fixes that and changes how the entries are stored in the organization. Each organization has a sub-group for folders and collections. For items which have a group, the respective group is created in the folders group of the organization. The collections are added as groups to the collection group.
This resembles the structure how it is presented in vaultwarden.