We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
A LSP Client may give us workspace/didRenameFiles notifications (if they support them).
workspace/didRenameFiles
{% render '$oldFileName' ... %}
{% render '$newFileName' %}
{{ $oldFileName | asset_url ... }}
{{ $newFileName | asset_url }}
{% section '$oldName' %}
We can do this with the workspace/applyEdit server->client request.
workspace/applyEdit
Obsidian & other note taking apps all do something like this, and a "Updated X links in Y files" popup seems like a neat thing to do as well.
The text was updated successfully, but these errors were encountered:
Oh... I just realized this needs VFS/full theme access.
Sorry, something went wrong.
Depends on #521
refactor.extract
Section (and eventually blocks) is more complicated. I'm going to split it out in a different issue.
charlespwd
Successfully merging a pull request may close this issue.
A LSP Client may give us
workspace/didRenameFiles
notifications (if they support them).{% render '$oldFileName' ... %}
to{% render '$newFileName' %}
from all files containing them.{{ $oldFileName | asset_url ... }}
to{{ $newFileName | asset_url }}
{% section '$oldName' %}
We can do this with the
workspace/applyEdit
server->client request.Obsidian & other note taking apps all do something like this, and a "Updated X links in Y files" popup seems like a neat thing to do as well.
The text was updated successfully, but these errors were encountered: