-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
[Feature Request] Pass additional context in URL #77
Comments
The plugin is already available like all other plugins via Storing the last query parameters is an easy feature. |
@Vinzent03 Sorry, I meant that while the plugin is accessible there isn't any (that I can see) fields exposed from the object that might contain information like the last query parameters. But that's a moot point I guess - adding a way to get the last query parameters is enough for me |
Does the new version help you? You can access via |
That's awesome, thanks for the update. I'll try it out this weekend! |
@Vinzent03 May I suggest to add the info into document ? |
Good idea! Done. |
Use Case
I'm starting to build a number of automations that leverage obsidian-advanced-uri to invoke commands (some external to obsidian, like via shortcuts, and some internal from buttons in dataview output).
For something like what I'm trying to do in #76, the flow ends up like:
My ultimate goal is to not have to navigate to the other file itself. I think this is possible if advanced-uri were enhanced like:
app.plugins.plugins['obsidian-advanced-uri
]This way, I could pass extra params like &taskfile=&taskline= and access them without the weird clipboard nonsense. I have both of those values at the time of creating my dataview table.
The text was updated successfully, but these errors were encountered: