Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can I bypass vault selection if I only have 1 vault? #35

Open
kenanmike opened this issue Jul 22, 2021 · 7 comments
Open

Can I bypass vault selection if I only have 1 vault? #35

kenanmike opened this issue Jul 22, 2021 · 7 comments
Labels
enhancement New feature or request

Comments

@kenanmike
Copy link

I only have one vault so would like to skip the step of having to choose the vault when it comes to creating a new empty note, for example. Is this possible?

@hauselin
Copy link
Owner

That's not possible right not. I'll consider implementing it in a future release.

@hauselin hauselin added the enhancement New feature or request label Jul 22, 2021
@kenanmike
Copy link
Author

kenanmike commented Jul 22, 2021 via email

@sanchitsharma
Copy link

Hey @hauselin, can I try working on this? I would like to add some other features too, like option add a note directly via alfred. But this seems a good starting point.

@hauselin
Copy link
Owner

hauselin commented Sep 4, 2021

Hey @sanchitsharma, yes, go ahead and take a stab at it! Thanks!

@sanchitsharma
Copy link

Thanks!!. Will do.

@sanchitsharma
Copy link

@hauselin I looked at the workflow in detail, and I think the best way to provide this functionality would be the following.
introduce two new variables - defaultVaultPath and defaultVaultName
add a new input "oadddefaultvault" to change/add the default vault name and path.
on addition of first new vault, it is automatically made the default vault as well (it can be changed via above input anytime later)
current "on" keyword is remapped to "onv" (v=vault)
"on" is now used to add directly to add to the default vault [Vault name shown in title by showing "Creating {query} in {defaultVaultName}]"

I have done a basic testing of above flow. Please let me know your thoughts.

@sanchitsharma
Copy link

@hauselin I looked at the workflow in detail, and I think the best way to provide this functionality would be the following.
introduce two new variables - defaultVaultPath and defaultVaultName
add a new input "oadddefaultvault" to change/add the default vault name and path.
on addition of first new vault, it is automatically made the default vault as well (it can be changed via above input anytime later)
current "on" keyword is remapped to "onv" (v=vault)
"on" is now used to add directly to add to the default vault [Vault name shown in title by showing "Creating {query} in {defaultVaultName}]"

I have done a basic testing of above flow. Please let me know your thoughts.

I am basing above thought on the philosophy that many users will like to have a default vault at least even if they they don't just have a single vault. Users with single vault will directly be able to use the functionality without any configuration. Also we can use the default vault config to add other default functionalities as well, example search etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants