Multiple androidapp:// go to AndroidApp, AndroidApp_1 and so on
Multiple URLs go to URL_1, URL_2 and so on
This mimics the way the KeePassDX app handles multiple URLs for it's autofill mechanism
This way, the RUN step that installs @bitwarden/cli gets cached and only needs to be run once per machine
Likewise for the RUN step that installs pykeepass, which only needs to be run when the pykeepass version gets bumped
In Bitwarden, one could make it so their account only has a certain set
of folders, like so:
- testfolder/a
- testfolder/a/b/c
- testfolder/a/b/c/d
The resulting hierarchy would look like this:
testfolder/a
`- b/c
`- d
As shown above, Bitwarden allows one to name a folder something like
"foo/bar" even if a folder "foo" doesn't exist. Bitwarden handles this
by just putting this folder in the root with the name as-is.
In addition, as shown with "testfolder/a/b/c", a folder name may not
necessarily be just anything that comes after the last `/` delimiter.
Instead, it's dependent on which ever existing folder happens to match
the most of the folder's name's prefix.
As such, the following references were used to replicate this behavior
in bitwarden-to-keepass:
ecdd08624f/common/src/services/folder.service.ts (L108)ecdd08624f/common/src/misc/serviceUtils.ts (L7)
When creating KeePass groups based off Bitwarden folders, make it so
that the KeePass groups follow the same hierarchy as their equivalent
Bitwarden folders.
