Originally created by @gerroon on GitHub (Jun 29, 2019).
Hi
According to this page subfolders can be creating with slashes but when I do that I do not get subfolders all I get a folder name with slashes, for instance
new folder work/teamA should createa work folder then a teamA folder but instead I get a folder named work/teamA
Originally created by @gerroon on GitHub (Jun 29, 2019).
Hi
According to this page subfolders can be creating with slashes but when I do that I do not get subfolders all I get a folder name with slashes, for instance
new folder
`work/teamA` should createa `work` folder then a `teamA` folder but instead I get a folder named `work/teamA`
Is this implemented or a missing feature?
https://help.bitwarden.com/article/folders/
thanks
Yep, that's expected. It's documented in the page you linked:
If a folder’s name contains the forward slash delimiter, yet no “parent” folder exists, its name will be displayed in its entirety.
I think we can close this? Feel free to reopen if there's more we can help with.
@mprasil commented on GitHub (Jun 29, 2019):
Yep, that's expected. It's documented in the page you linked:
> If a folder’s name contains the forward slash delimiter, yet no “parent” folder exists, its name will be displayed in its entirety.
I think we can close this? Feel free to reopen if there's more we can help with.
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.
Originally created by @gerroon on GitHub (Jun 29, 2019).
Hi
According to this page subfolders can be creating with slashes but when I do that I do not get subfolders all I get a folder name with slashes, for instance
new folder
work/teamAshould createaworkfolder then ateamAfolder but instead I get a folder namedwork/teamAIs this implemented or a missing feature?
https://help.bitwarden.com/article/folders/
thanks
@gerroon commented on GitHub (Jun 29, 2019):
Ok it seems like the top folder has to exists this to work.
@mprasil commented on GitHub (Jun 29, 2019):
Yep, that's expected. It's documented in the page you linked:
I think we can close this? Feel free to reopen if there's more we can help with.